ITMS-90562: Invalid Bundle with Xcode 13.3 RC

When archiving and uploading a build of our tvOS app to App Store Connect with Xcode 13.3RC, it gets rejected with

TMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path.

When archiving and uploading with Xcode 13.2.1 the build is accepted and processed.

I could not find any rpath issues when inspecting the binary with otool -L and otool -l.

Has anyone else experienced the this issue with Xcode 13.3RC?

I've filed feedback FB9952607

Answered by DTS Engineer in 708133022

New apps uploaded to the App Store as of today (March 22, 2022) should no longer encounter the original error reported upon upload in relation to using Swift concurrency:

ITMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path.

If you were previously impacted, please upload a new version today. If you continue to receive this error message, please let us know through Feedback Assistant, and post the FB number here.

The only thing that worked for me, unfortunately is downgrading to Xcode 13.2.1

Same here v13.3 (13E113)...

Same here. Disable bitcode it's a very bad solution and also downgrade to Xcode 13.2.1.

Apple must fix and allow us to work.

Disabling Bitcode looks like it works. But then running that build from TestFlight on a iOS 14 device, and it will crash on launch. When run through Xcode in that same device it doesn’t crash.

got a reply on the DTS ticket. They just pointed to the release notes and disable Bitcode work around. They ignored where I said doing that work around just causes the app to crash.

Same issue v13.3(13E113)

any solutions now?

The only thing I’ve confirmed that works is changing the deployment target to >= iOS 15.0, or deleting all Swift concurrency support. I tested both, but I have settled on dropping Swift concurrency support. Maybe I will try it again in a few years after others have figured out the issues.

We had to downgrade our Xcode version to 3.2.1. Super frustrating experience here. Apple should update their release notes to let users know about this issue and the work around as this completely blocked us from submitting to the App Store.

Same issue here

I am having the same issue. I am concerned about the "fix". Isn't bitcode actually an important feature for optimizing the download from the app store. So while disabling it might fix the problem, might it not impact the user experience - at least in terms of the download?

With that in mind, I'm sadly waiting to ship my new version for a bit and hoping Apple releases a fixed version soon...

Hopefully our friends at Apple will know that we are still waiting for a solution.

I found that I had this issue building with xcodebuild but not when building and deploying interactively through Xcode and Organizer. Did not have to adjust bitcode settings and did enable bitcode on upload. Looking at the binary executable, there is a clear 43MB difference in size between the accepted version (bigger) and the command line built version. Would be interested to know if anyone else has seen this.

Accepted Answer

New apps uploaded to the App Store as of today (March 22, 2022) should no longer encounter the original error reported upon upload in relation to using Swift concurrency:

ITMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path.

If you were previously impacted, please upload a new version today. If you continue to receive this error message, please let us know through Feedback Assistant, and post the FB number here.

First I fixed it by downgrading to Xcode 13.2.1, now we removed iOS 13 support and went back to Xcode 13.3 and it works without a problem.

Fixed by Apple. My builds are OK Now

ITMS-90562: Invalid Bundle with Xcode 13.3 RC
 
 
Q