I've tried removing the arm64e slice from the /SwiftSupport version after archiving the app, then letting Xcode create a build for the App Store, but exporting it, and both versions seem the same. However after uploading, I still get the error.

Success. I finally got a build to be accepted. I set ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = NO for the watch target. I don't know how this might affect the actual running of the watch app, as I no longer have an Apple Watch to test it on, but the iOS app is running fine through TestFlight.

It works fine with Xcode 14.1 RC2

I'm now getting this with Xcode 14.2

Never mind. It seems Xcode had signed me out of my new dev account.

Yes I also noticed it has user login issues. I've recreated all my bots with 14.2 again but now they fail to checkout with auth failure and after 2 hours i'm on the verge of giving up. It's funny how all the Xcode Server bug reports i've submitted have all occurred since Xcode Cloud was introduced and none have had a single reply.

It seems that Apple have deprecated Xcode Server, hence all the issues and no replies to bug reports. I've resigned myself to the fact that we must use Xcode cloud now and have my bot tests working their... Until they start charging, then i'll look for an alternative.

Did you ever figure out how to format the NFC tag?

I have attached a sysdiagnose from my iPhone after the crash.

Wow, this was as simple as adding a @Sendable keyword! I posted about this last month here: https://forums.developer.apple.com/forums/thread/763790 I also submitted a bug report #FB15145734 as I assumed the block was being run on the incorrect thread which was out of our control. Happy to have this working now, but I do wonder is this still an issue with the function, or simply a Swift 6 compiler issue?

Turns out this was fixed by simply marking the completion block @Sendable. https://developer.apple.com/forums/thread/764874?answerId=810243022#810243022

I'm also suffering from this problem. Has anyone figured out a solution?

I'm having exactly the same issue. I can't test a purchase locally. Did you ever get it working?