Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Store Connect ITMS-90562: Invalid Bundle issue #347

Closed
maxlapides opened this issue Sep 1, 2021 · 12 comments
Closed

App Store Connect ITMS-90562: Invalid Bundle issue #347

maxlapides opened this issue Sep 1, 2021 · 12 comments

Comments

@maxlapides
Copy link

Hi there! I'm not sure if there is a better place to file this issue, but when we upgrade to the latest versions of the MLKit dependencies, App Store Connect rejects our iOS app with this error:

ITMS-90562: Invalid Bundle - The app cannot be processed because options not allowed to be embedded in bitcode are detected in the submission. It is likely that you are not building the app with the toolchain provided in Xcode. Rebuild your entire app with the latest GM Xcode and submit the app again.

This issue seems to be the same: rmtmckenzie/flutter_qr_mobile_vision#183

Is there some way to update the GoogleMLKit/BarcodeScanning to support bitcode in iOS builds?

@bcdj
Copy link
Collaborator

bcdj commented Sep 2, 2021

Which version of xcode are you using? Can you try xcode 12.4 to see if the same issue happens?

@maxlapides
Copy link
Author

@bcdj I'm using Xcode 12.5.1. I just tested rebuilding the app with Xcode 12.4 and uploaded it to TestFlight. Unfortunately, I got the same processing error.

@maxlapides
Copy link
Author

maxlapides commented Sep 2, 2021

This is my Podfile.lock diff. The old version is working, the new version is rejected by the App Store.

Screen Shot 2021-09-01 at 9 39 01 PM

@Jarutais
Copy link

Jarutais commented Sep 2, 2021

I'm having the same issue with pod 'GoogleMLKit/SegmentationSelfie', '2.3.0'
It was uploading successfully with previous versions of the framework.

@miworking3
Copy link
Collaborator

Thanks for the information, this is our top priority right now.
If this bitcode issue comes from building time, the best solution would be to fix it on the next release, which will be about 1 month later, unless there are any stop-gap that can be applied.

@miworking3
Copy link
Collaborator

FWIW, does this help?
https://stackoverflow.com/questions/49642653/xcode-9-3-cannot-submit-build-to-app-store/50805000#50805000
You can try to rebuild the app from bitcode by yourself and that might give you some more informations. To do that in Xcode archive your app, then in organizer, in archives tab click "Distribute App", select "Development", and after that select "Rebuild from Bitcode" and proceed. After that Xcode will probably show more extended information about the problem which might help you solve it.

@Jarutais
Copy link

Jarutais commented Sep 2, 2021

FWIW, does this help?
https://stackoverflow.com/questions/49642653/xcode-9-3-cannot-submit-build-to-app-store/50805000#50805000
You can try to rebuild the app from bitcode by yourself and that might give you some more informations. To do that in Xcode archive your app, then in organizer, in archives tab click "Distribute App", select "Development", and after that select "Rebuild from Bitcode" and proceed. After that Xcode will probably show more extended information about the problem which might help you solve it.

I got this error

Captura de Tela 2021-09-02 às 16 43 20

@miworking3
Copy link
Collaborator

I see, this error will require to disable the bitcode if that's acceptable:
https://developer.apple.com/forums/thread/662947

Apple Clang - Code Generation --> "ENABLE CODE COVERAGE SUPPORT" need to set "NO" and

Build Option --> "ENABLE BITCODE" need to set "NO"

@maxlapides
Copy link
Author

Unfortunately, I don't think this solution is acceptable for us. Shipping our app to the App Store with bitcode helps us minimize the download size of our app. Also, it is likely that bitcode will eventually be required to submit apps to the App Store.

@miworking3
Copy link
Collaborator

Understand, thanks for verifying that.

@bcdj
Copy link
Collaborator

bcdj commented Sep 4, 2021

We are working on a fix and plan to ship it in our next release at the end of the month. A temporary workaround is to use the previous release. For example, to use barcode scanning, you can have the following in your Podfile: pod 'GoogleMLKit/BarcodeScanning', '2.2.0', and for selfie segmentation, you can use the following in your Podfile: 'GoogleMLKit/SegmentationSelfie', '2.2.0'.

@bcdj
Copy link
Collaborator

bcdj commented Sep 28, 2021

ML Kit just shipped a new release. This issue is now fixed. Please download the latest ML Kit release using a Podfile similar to the one in our vision quickstart sample app. Thank you for your patience!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants