How to debug “Invalid Bundle” error which happens only after submitting to app store

Question

I have a lot of frameworks in my app. App works fine in adhoc/enterprise release. Only if I submit to the app store for testflight testing I get this error email from apple:

Answer 1

I had the same problem, it was due to one framework not being present in the Frameworks subfolder in the app bundle.

I fixed it by adding a Copy Fields build phase, and adding the missing .framework file there.

Answer 2

Had same issue. This happened to me because one of my Framework target was added to main target in "Link Binary With Libraries" but was not added to "Target Dependencies" and "Embedded Binaries"

Answer 3

Tried all the above solutions and did not work for me.

I was experiencing this issue in Xcode 10.1 recently and all my frameworks were referenced correctly (did otool -L and everything lined up).

Seems there were some changes in the apple validation process, may be a bug, may not be on Apple's end, but all my prior builds uploaded and validated fine -- and I did not add any new frameworks since.

Upon uploading the binary to iTunesConnect, I'd see the following error:

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

Invalid Bundle - The app uses Swift, but one of the binaries could not link to it because it wasn't found. Check that the app bundles correctly embed Swift standard libraries using the "Always Embed Swift Standard Libraries" build setting, and that each binary which uses Swift has correct search paths to the embedded Swift standard libraries using the "Runpath Search Paths" build setting.

MY SOLUTION:

• After days of debugging, what worked for me was to disable 'Include bitcode for iOS content' upon uploading the archive from Xcode organizer. Seems that this option modifies the binary which caused the validator to fail.

• Or you can disable bitcode in your Build Settings

Answer 4

This error message is also addressed in Apple Technical Note TN2435 Embedding Frameworks In An App: https://developer.apple.com/library/archive/technotes/tn2435/_index.html

You can find the error message under the heading "Missing Framework Bundle" with troubleshooting steps.

Answer 5

So I struggled on this for two days. What it turned out to be was I had UITests checked in Archive for the Build for the Scheme I was archiving.

After unchecking it from Archive, re-archiving it, validating it (although validating it before always passed), and "Upload to AppStore" I did not get the e-mail from Apple informing me of Invalid Swift Support. Instead I got the e-mail that it'd been processed and is good to go!

Answer 6

In my case, in the build settings, this was fixed when I added the following to the build settings for the library:

 DYLIB_INSTALL_NAME_BASE = @rpath

The clue was a linker warning: 'YourLibrary has an install name beginning with “/”, but it is not from the specified SDK'