You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was a thread in the Expo forums on how iOS builds were being rejected by the App store due to the following 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.
The solution was to pin the GoogleMLKit/TextRecognition pod to version 2.2.0 per Google's release notes [here](GoogleMLKit/TextRecognition pod). This solves the build issue, but the downside is that it uses MLKit's Text Recognition v1 instead of Text Recognition v2 (in beta).
Currently, I applied this solution in my project project using patch-package, but are we open to pinning the version number to 2.2.0 in the .podspec file here? It's a simple code change and I'd like to make it & contribute if possible.
Thanks!
The text was updated successfully, but these errors were encountered:
Kommandat
changed the title
iOS builds not approved by App Store connect due to unpinned GoogleMLKit/TextRecognition version
iOS builds not approved by App Store due to unpinned GoogleMLKit/TextRecognition version
Sep 11, 2021
@agoldis is pinning the right thing to do? Because it makes it use old version of text recognition. Does it only affect certain react-native versions? Or does it affect all?
There was a thread in the Expo forums on how iOS builds were being rejected by the App store due to the following error:
The solution was to pin the GoogleMLKit/TextRecognition pod to version 2.2.0 per Google's release notes [here](GoogleMLKit/TextRecognition pod). This solves the build issue, but the downside is that it uses MLKit's Text Recognition v1 instead of Text Recognition v2 (in beta).
Currently, I applied this solution in my project project using patch-package, but are we open to pinning the version number to 2.2.0 in the .podspec file here? It's a simple code change and I'd like to make it & contribute if possible.
Thanks!
The text was updated successfully, but these errors were encountered: