Ah. There was a user setting VALID_ARCHS that I think an old Xcode upgrade created (I certainly didn't). It's a very old project.

I get this a lot too. Filed FB9807088

We just ran into this today. We also have no watchOS component in our app. Currently have a support ticket open with Apple, they're escalating it.

Same here with Xcode 13.2.1. FB9828542 Apple, you need to stop abandoning things before we all have access to a replacement.

I still frequently encounter this issue today with Xcode 13.

I see this behavior, too, in Xcode 13.2

Interestingly, running --upload-package a second time, hours later, results in this: Getting list of providers... Beginning delivery... Resuming package upload to the App Store… Requesting upload instructions from the App Store… Completing upload… File 'OurApp.ipa' complete. Uploaded asset is processing. No errors uploading '../exports/OurApp.ipa' And the app is now uploaded and processing.

I needed the G4 certificate from here. Maybe because it’s a year later from when the above solution was posted? In any case this is pretty messy.

@eskimo I was unable to import into "login", "System", or "iCloud" keychains, but was able to import into "accountsKeychainExport". What is that? It seems very sus. In any case, I have TWO of these "accountsKeychainExport" keychains in my system, and both are empty, even after import. I had the inspiration to try dragging the .cer file from the Finder into my login keychain, and that seemed to work, but it says the certificate is not trusted: (I’ve redacted identifying info; note that the selected cert replaces the last cert in that list, set to expire in a month.) Ah, I had to DL a newer Apple intermediate certificate from here (specifically, the G4 cert). That seems clunky. macOS 21F79 on M1 Max MBP.

@eskimo Enhancement request: FB11800863

Oh I'm quite aware that the sample code isn't intended to be a "real" application; I only used it to test the approach, and to see if it was any better than Parallels at the same task (it is, because I was able to directly create the VM from the the beta image). In fact, it was very exciting to have so much functionality in sample code. What's lacking is Parallels' VM. It doesn't share the clipboard, and doesn't allow dragging and dropping of files between the host and guest Finders, something that does work for the other guest OSes like Windows. What is lacking in the macOS virtualization framework is documentation. It's not clear, for example, how one would change the display configuration of a running VM (e.g. in response to a VM window size change), or how to set up the shared clipboard, or what a "memory balloon" device is. I've already filed a bug about not being able to log into iCloud, which has also been reported on this forum by many others. FB12006346 Looking at the Console, it definitely seems to be a self-signing issue. So I go to sign my app, but I can't. I don't know why, but I get errors saying it couldn't communicate with Apple, which seems unlikely, and that no provisioning profile for my app was found. But it's supposed to be managing that automatically. THIS IS TOO HARD.

I just ran into this problem, a year later. I'd happily let Xcode handle this, but it fails.

Still fails, unfortunately.

I created a brand new Multiplatform project. Built and ran it for macOS, then Archived it. Tried same steps as above to export it: Archive, Distribute App: Developer ID -> Export -> Automatically Manage Signing -> FAIL I get the same failure: Communication with Apple failed You are not allowed to perform this operation. Please check with one of your Team Admins, or, if you need further assistance, please contact Apple Developer Program Support. https://developer.apple.com/support No signing certificate "Developer ID Application" found No "Developer ID Application" signing certificate matching team ID "" with a private key was found.

Confusingly, Xcode shows both a "Personal Team" and a team for my LLC. I always use the LLC, and I have only one login in the developer portal/app store connect. Both of these attempts were using my LLC team.