BiometricPrompt is not hiding if error code is different than ERROR_CANCELED or BiometricPrompt.ERROR_LOCKOUT [143683687]

Fixed

Bug

Status Update

No update yet.

Description

te...@gmail.com

created issue #1

Oct 31, 2019 04:08PM

BUILD INFO
- Device type:
- OS version:
- Biometric library version: 1.0.0-rc02

STEPS TO REPRODUCE
[Be as specific as possible please]
Write robolectric test
1. Show BiometricPrompt
2. Invoke onAuthenticationError(BiometricPrompt.ERROR_HW_UNAVAILABLE, "some message")

EXPECTED RESULTS
prompt should be dismissed because no further authentication can take place

OBSERVED RESULTS
prompt is not dismissed

Comments

cu...@google.com <cu...@google.com> Oct 31, 2019 07:20PM

Reassigned to cu...@google.com.

cu...@google.com <cu...@google.com> #2Nov 1, 2019 11:35PM

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?

te...@gmail.com <te...@gmail.com> #3Nov 4, 2019 09:43AM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

cu...@google.com <cu...@google.com> Nov 5, 2019 11:58PM

Accepted by cu...@google.com.

ap...@google.com <ap...@google.com> #4Nov 6, 2019 05:25PM

Marked as fixed.

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.

an...@google.com <an...@google.com> #5Nov 26, 2019 06:07PM

Hmm, I feel the crash might be something related to separate/secondary process.

I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.

Issue 143683687