-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Bug report] SIGILL crash libmlkit_google_ocr_pipeline.so on certain devices #655
Comments
Hi there, sorry for the late reply! Question: do you have platform configuration(32bit v.s. 64bit) when building the apk? Going forward google play services support 32bit and 64bit devices, but wont support mismatch case: meaning 32bit binary running on 64bit devices or 64bit binary running on 32bit devices. see https://android-developers.googleblog.com/2019/01/get-your-apps-ready-for-64-bit.html |
Hi, I'm building the bundle only for 'armeabi-v7a' and 'arm64-v8a' |
Actually sorry for this regression, we verified this issue fixed in a Moto e7i and will have that in the upcoming release soon. |
|
Hi, I tried it with the new |
Mi |
Describe the bug
On certain devices SIGILL is caused when trying to use com.google.mlkit.vision.text.TextRecognizer.
Crash log:
To Reproduce
Using
com.google.mlkit.vision.text.TextRecognizer
on devices like Moto e7iThe last v2 text recognition lib causes the crash
com.google.mlkit:text-recognition:16.0.0-beta6
No crash with
com.google.mlkit:text-recognition:16.0.0-beta5
Everything works fine also when using the old v1
com.google.android.gms:play-services-mlkit-text-recognition:18.0.2
Expected behavior
It shouldn't crash
SDK Info:
com.google.mlkit:text-recognition:16.0.0-beta6
Smartphone:
~100 of users affected by the crash in less than one week, I could also reproduce it locally on Moto e7i device.
Devices from Play Console crash report:
Android versions: 10, 11, 12
The text was updated successfully, but these errors were encountered: