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

Up vote post of _tom_ Down vote post of _tom_
11k views
Posted by
_tom_
Reply

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

    —
    madjuju

  • same issue with Version 13.3 (13E113) too

    —
    tenCats_hdt

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

    —
    JFER

Apple Recommended

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.

Posted by
edford
Up vote reply of edford Down vote reply of edford
Post marked as Apple Recommended Post marked as solved

  • Still getting the error. FB9964419

    —
    treyrich

  • thanks, it works now

    —
    diamont1001

  • Fixed for me

    —
    madjuju

Replies

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.

Posted by
AndrewM
Up vote reply of AndrewM Down vote reply of AndrewM

  • DTS ticket burned. 😂

    —
    Gong
Add a Comment

any solutions now?

Posted by
diamont1001
Up vote reply of diamont1001 Down vote reply of diamont1001
Add a Comment

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.

Posted by
AndrewM
Up vote reply of AndrewM Down vote reply of AndrewM
Add a Comment

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.

Posted by
nissenbaumdaniel
Up vote reply of nissenbaumdaniel Down vote reply of nissenbaumdaniel
Add a Comment

Same issue here

Posted by
sommerlund
Up vote reply of sommerlund Down vote reply of sommerlund
Add a Comment

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...

Posted by
skapur1424
Post not yet marked as solved Up vote reply of skapur1424 Down vote reply of skapur1424
Add a Comment

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

Posted by
Gong
Up vote reply of Gong Down vote reply of Gong
Add a Comment

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.

Posted by
Purple Monkey 42
Up vote reply of Purple Monkey 42 Down vote reply of Purple Monkey 42

  • I did have the issue with building and deploying through Xcode 13.3 and Organizer. I don't know how to do it with the command line.

    —
    skapur1424

  • I suspect I tried before and after Apple fixed the glitch today maybe. otool -L showed no differences and we are using concurrency.

    —
    Purple Monkey 42
Add a Comment

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.

Posted by
edford
Up vote reply of edford Down vote reply of edford
Post marked as Apple Recommended Post marked as solved

  • Still getting the error. FB9964419

    —
    treyrich

  • thanks, it works now

    —
    diamont1001

  • Fixed for me

    —
    madjuju

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.

Posted by
leohidalgo
Up vote reply of leohidalgo Down vote reply of leohidalgo
Add a Comment

Fixed by Apple. My builds are OK Now

Posted by
madjuju
Up vote reply of madjuju Down vote reply of madjuju
Add a Comment

Have you guys tested the app built and uploaded in Xcode 13.3 on iOS 14? Not local testing, but uploading to Connect then downloading and installing via App Store or TestFlight.

I found that all my UITests for iOS 14 on Xcode Cloud crashed and failed.

Posted by
Gong
Up vote reply of Gong Down vote reply of Gong
Add a Comment

Same for us, using new Xcode 13.3 the app uploaded to testflight crashes on iOS 14 devices (

Posted by
OlegMetallic
Up vote reply of OlegMetallic Down vote reply of OlegMetallic
Add a Comment

Seeing this for our app. FB9970868

Posted by
Smithers
Up vote reply of Smithers Down vote reply of Smithers
Add a Comment

I've gone through every single framework / plugin / binary in the app bundle with otool -L and found nothing. What's annoying is how these emails about "ITMS-90562: Invalid Bundle" do NOT in fact tell us what's invalid in the bundle - if you (i.e. the processing server) are aware, why not just tell us in the same email?

I've tried it with Xcode 13.2.1 as well and it still gets rejected. I have no idea what's going on as another one of our apps is submitting fine.

Posted by
Smithers
Post not yet marked as solved Up vote reply of Smithers Down vote reply of Smithers
Add a Comment