Fixed
Status Update
Comments
20...@gmail.com <20...@gmail.com> #2
A couple of questions:
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
cu...@google.com <cu...@google.com>
kc...@google.com <kc...@google.com>
ap...@google.com <ap...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
pr...@google.com <pr...@google.com> #4
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
Description
"Android 9 only includes fingerprint integration for BiometricPrompt. However, integrated support for other biometric modalities are forthcoming." - is it forthcoming to Android 9 and above, or to Android 10 and above?
"On devices running P and above, this will show a system-provided authentication prompt, using a device's supported biometric (fingerprint, iris, face, etc)." - we tested this on Galaxy S10, S9, S8, all of which are currently on P and all of which has a system setting for iris / face id, and got a fingerprint dialog only with BiometricPrompt. So again, is iris/face supposed to work on Android 9 with this API? Or is the issue that Samsung's sensors are considered "weak biometrics" so they will never be supported by BiometricPrompt? Is there a strong biometrics device on the market (besides the upcoming Pixel 4) to which face support is coming with BiometricPrompt on Android 9?