Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
BUILD INFO
STEPS TO REPRODUCE
EXPECTED RESULTS The AuthenticationCallback provided to BiometricPrompt is called appropriately
OBSERVED RESULTS The AuthenticationCallback is not called at all
NUMBER OF TIMES YOU WERE ABLE TO REPRODUCE (e.g. 3/10) 10/10
ADDITIONAL INFORMATION Because the part of the BiometricPrompt code is implemented differently on different distributions of the Android OS, it is possible that this same bug can occur when authenticating from the fingerprint/biometric screens as well as on the device credential screen (e.g. some Samsung devices appear to use an Activity for the fingerprint/biometric screen, which causes this same issue to occur). However, using an emulator with Android 10 and the device credentials flow is the easiest way to reproduce this bug.
This same bug does not occur if the platform's
android.hardware.biometrics.BiometricPrompt
is used instead.Below is some example code for an Activity that will reproduce the issue describe above. In this example, you would expect to see a toast if the AuthenticationCallback was called successfully.