Status Update
Comments
an...@gmail.com <an...@gmail.com> #2
I'm seeing this as well, and it's happening after navigating to a screen that does not even use compose dependencies. Our flow is:
Non Compose fragment -> Compose fragment -> Non compose fragment -> This crash immediately
Currently troubleshooting, but coming up empty and cannot reproduce on my device, but seeing crashes on client devices.
Non Compose fragment -> Compose fragment -> Non compose fragment -> This crash immediately
Currently troubleshooting, but coming up empty and cannot reproduce on my device, but seeing crashes on client devices.
Description
Some Xiaomi devices do not handle properly the credential fallback. Pressing the fallback button of the prompt or using the wrong finger to trigger the automatic credential fallback cause an immediate
BiometricPrompt.ERROR_CANCELED
(5) to be emitted. The credential activity starts regardless, but its result, be it success or failure, won't be passed back to the application.I could work around this issue by forking the androidx library and forcing this condition to be true for Xiaomi devices.
launchConfirmCredentialActivity()
is going to show theBiometricPrompt
and it will handle the credential fallback correctly.So far I managed to reproduce the issue on a Redmi Note 8 Pro with Android 10. Not all the Xiaomi devices behave incorrectly, but I have no more info on this.
This appears to be the behavior of the native
BiometricPrompt
, so it is probably a vendor specific bug, but it is probably worth implementing some workaround in the library if feasible.Here some information on the device affected by the issue: