ITMS-90562: Invalid Bundle with Xcode 13.3 RC

Same issue here. The error message "TMS-90562: Invalid Bundle" is incorrect and misleading. When you try to use Ad Hoc distribution to export an IAP, you will find real problems related to the latest SDK and Bitcode.

See Unable to export for Ad Hoc or Development distribution with Xcode 13.3 RC

Hello, Same issue here

Same issue here with Xcode 13.3 (13E113) release :(

I just burned a DTS ticket on this, and also linked to this thread. Hopefully that gets a response soon.

Maybe it can help someone: I found libswift_Concurrency.dylib in the Frameworks directory of my package which is unexpected (my project is ios Only) . I remove it from the archive and I can now process an ad hoc distribution.

I have not uploaded it to appstoreconnect

Same issue and same framework in the Frameworks directory as the comment above. Can't find a solution.

I found a known issue in Xcode 13.3 Release Notes that might explain this issue:

Exporting an app that uses Swift’s concurrency features from an archive with bitcode might fail when the app targets iOS 13.0 – iOS 14.7, watchOS 6.0 – watchOS 7.6, or tvOS 13.0 – 14.7. (89271047)

Workaround: Either uncheck the box Rebuild from bitcode when exporting the app from an archive or disable bitcode (iOS only).

Can't seem to get the workaround to work for me, because I can't find the 'Rebuild from bitcode' checkbox and disabling bitcode is not an option (app is not only iOS). Setting 'Enable Bitcode' to 'No' inside Xcode for all targets where it's possible, does not fix the issue.

Disable bitcode works for me.

Disabling Bitcode sadly is not a fix if you have a WatchOS app

Switching the deployment target from watchOS 7.0 to watchOS 8.0 fixed the issue for my watchOS app. I know that might not be a viable solution for everyone.

It's really, really annoying, I have 26 applications affected. Very bad day and very bad idea to have updated Xcode!

Disabling Bitcode works but next my appclip binary was too large. It's not an optimal and suitable solution for long term

same issue with release version : Version 13.3 (13E113)

I wouldn't disable Bitcode to work around this. Bitcode allows your app to be recompiled for specific devices and iOS versions which makes the app package as small as possible when users download it from the App Store. Instead do all of this:

• Remove libswift_Concurrency from all of your targets (Target ⇢ Build Phases ⇢ Link Binary With Libraries)
• Remove libswift_Concurrency from the Frameworks group in the Project Navigator
• Remove all Swift concurrency keywords from your sources: @MainActor, async, await, etc

According to the release notes this only happens when the app targets <iOS 15, so presumably all of your users weren't getting these features to begin with and you were already branching on availability of iOS 15. If you're like me, you were doing this to get the subscription management screen in iOS 15 but thanks to this Xcode 13.3 regression your users won't get that even on iOS 15.

same issue with Version 13.3 (13E113) too