Xcode - Error Itms-90635 - Invalid MACh-O in Bundle - Submitting to App Store

Xcode - Error ITMS-90635 - Invalid Mach-O in bundle - submitting to App store

I had the same problem earlier this morning. In fact the answer is in the error : "Verify that all of the targets for a platform have a consistent value for the ENABLE_BITCODE build settings"

I had a target (with ENABLE_BITCODE set to NO), using multiple pods having ENABLE_BITCODE set to YES. So, all I had to, do is set ENABLE_BITCODE to YES in my project target. But I guess you have a choice, you can also set ENABLE_BITCODE to NO in all the libs your are using.

Sudden Error when Uploading to iTunesConnect: ITMS-90635 Invalid Mach-O Format / ENABLE_BITCODE

I finally was able to do it, with one of the solutions from this post https://stackoverflow.com/a/37624641/2702513

What I had do do, was stripping the Bitcode from my library, which can be done with this command:

$ xcrun bitcode_strip -r {PATH_TO_LIBRARY} -o tmp.dylib

The command extracts the machine code from the library into the tmp.dylib file which then can be used instead of the library itself. In case of PSPDFKit the library is inside the framework.

iOS app distribution failed with error ITMS-90635 nested bundle contains arm64(machine code) whereas main bundle contains arm64(bitcode)

Ok, I finally found what was wrong :)

Once lipo done, I used to copy/paste

Build/Products/Release-iphoneos/MyFramework.framework/Modules/MyFramework.swiftmodule/

into

Build/Products/Release-iphonesimulator/MyFramework.framework/Modules/MyFramework.swiftmodule/

and then I was distributing this final framework:

Build/Products/Release-iphonesimulator/MyFramework.framework.

Do the opposite! Once lipo done, copy/paste MyFramework.swiftmodule/'s Release-iphonesimulator/ into the Release-iphoneos/ one and distribute the .framework in Release-iphoneos/.

ERROR ITMS - 90167 No. app bundles found in the package

After chatting with folks at WWDC in both the Xcode lab and the App Store lab, they were able to dig up information that this is a known issue in the current Sierra seed that is fixed in the next release. You can either revert, or wait. Not the most satisfying answer, I admit.

---

Related Topics