I've been battling with this issue too. I have more information over at stackoverflow - https://stackoverflow.com/questions/66012056/xcode-server-bot-not-sending-email-reports?noredirect=1#comment117216210_66012056 I think i've narrowed it down to a permission issue which can't be fixed as in Big Sur the root is read only. I've found that Xcode post scripts can in fact run postman directly, so I will be posting an update later with how I got it working using postman directly.

Ok, it seems this only happens when building for the simulator. Which isn't really an issue. When I archive the app, it builds with bitcode just fine.

I've been having the same today updating Numbers, Pages and iMovie. Each one has taken many hours to install!

I’m trying to run my iOS app unmodified on an M1 Mac. So that explains why the macCatalyst check doesn’t pass. But why does the iOS 15+ check succeed when it even reports it’s running as iOS 14.7?

Did you have any luck with this? I am developing an iOS 15+ SwiftUI app and want to display the BluetoothAccessoryPicker but it just does not show! I've tried adding the AppDelegate to my app and try to show the picker using: try await manager.showBluetoothAccessoryPicker(withNameFilter: nil) But I get nothing, just these lines in the console log: 2021-10-18 11:47:52.905742+0100 MyApp[18402:2620972] IAPAppRegisterClient: capabilities 0x8030 2021-10-18 11:47:52.906019+0100 MyApp[18402:2620972] IAPAppRegisterClient: __eaClientRegisterediapd 0 -> 1 2021-10-18 11:47:52.906085+0100 MyApp[18402:2620972] IAPAppRegisterClient: __eaClientRegisterediap2d 0 -> 1 2021-10-18 11:47:52.906700+0100 MyApp[18402:2620972] IAPDHasLaunched: kIAPAvailableNotification iapdAvailableState 100 -> 0 2021-10-18 11:47:52.906806+0100 MyApp[18402:2620972] IAPAppRegisterClient: __eaiapdHasClientID 0, IAPDHasLaunched 0 2021-10-18 11:47:52.907168+0100 MyApp[18402:2620972] IAP2DHasLaunched: kIAP2AvailableNotification iap2dAvailableState 100 -> 0 2021-10-18 11:47:52.907238+0100 MyApp[18402:2620972] IAPAppRegisterClient: __eaiap2dHasClientID 0, IAP2DHasLaunched 0 2021-10-18 11:47:52.907416+0100 MyApp[18402:2620972] IAPAppRegisterClient: registerWasSuccessful 0 2021-10-18 11:47:52.907716+0100 MyApp[18402:2620972] -[EAAccessoryManager _initFromSingletonCreationMethod] isRunningOnMac 2021-10-18 11:47:52.910422+0100 MyApp[18402:2620972] IAPAppConnectedAccessories: __eaClientHasCheckedForConnectedAccessories 0 -> 1 2021-10-18 11:47:52.910760+0100 MyApp[18402:2620972] IAPAppConnectedAccessories: IAPDHasLaunched 0, IAP2DHasLaunched 0 2021-10-18 11:47:54.170507+0100 MyApp[18402:2620954] Writing analzed variants. The very last line only appearing when I try to show the picker.

Ok, I guess I fixed it, for now. Even though i'd tried rebooting the Mac, closing Safari then trying this login did in fact open Safari correctly. It even presented me with the 30+ login windows that had previously not opened. So it's working again now, but I don't know why it got stuck.

Still the same. See attached image of me resigning. The signature changes, but not the version.

darrenjones@macbook-pro ios-arm64_armv7 % file MTGSDK.framework/MTGSDK MTGSDK.framework/MTGSDK: Mach-O universal binary with 2 architectures: [arm64:current ar archivecurrent ar archive] [arm_v7] MTGSDK.framework/MTGSDK (for architecture arm64): current ar archive MTGSDK.framework/MTGSDK (for architecture armv7): current ar archive The frameworks are a third party Ad framework: here

I hope everyone is filing bug reports for this.

Did you ever figure this out? I am getting a lot of Code=306 "Reached max retry count" errors in Production when users attempt to make a purchase. Apple can't fix/debug it unless I can provide a way to reproduce it.

The lib swift_Concurrency.dylib framework contains the arm64e architecture, but my watchOS binary does not. I wonder if this is the problem, and if so, why?

Nope, tried removing arm64e architecture from /Payload/MY_APP.app/MY_APP_WatchOS.app/libswift_Concurrency.dylib but still get the same error. /SwiftSupport/watchos/libswift_Concurrency.dylib: contains: armv7k arm64_32 arm64 arm64e size: 30594960 /Products/Applications/MY_APP.app/Watch/MY_APP_WatchOS.app/Frameworks/libswift_Concurrency.dylib also contains: armv7k arm64_32 arm64 arm64e size: 2224144

Ok, so regardless of me changing the architectures in: /Products/Applications/MY_APP.app/Watch/MY_APP_WatchOS.app/Frameworks/libswift_Concurrency.dylib as soon as I let Xcode do whatever it does when hitting "Distribute App", it removes the arm64e architecture from the watch app framework, but leaves it in the /SwiftSupport/watchOS/libswift_Concurrency.dylib version. So they will never match! Please, how can I fix this?

This is getting frustrating now. I've tried adding arm64e as an architecture to my watchOS app, but now get an error that it's an invalid implementation.

I've tried so many builds and none work. After letting Xcode package to upload, both the /SwiftSupport/watchOS/libswift_Concurrency.dylib and /Payload/MY_APP.app/Watch/MY_APP_WatchOS.app/Frameworks/libswift_Concurrency.dylib files contain the same swift version 5.7.1, however the one in /SwiftSupport contains the arm64e slice but the other one doesn't. I can't get Xcode to export the build without arm64e and I'm not sure if I can just remove it from the .app or whether the signature will then be invalid?