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)
Attachment actions
Unintended behavior
View staffing
Description
BUILD INFO
- Device type: Google Pixel 4
- OS version: Android 13, API 33
- Biometric library version: 1.1.0
STEPS TO REPRODUCE
The bug affects only devices that use a passive biometric type where the "setConfirmationRequired(true)" is applicable. In this case, for Google Pixel 4 the passive biometric is the face.
The important step is #4.
1. Use a device that supports face recognition as a biometric type, so in our case this is a Pixel 4 which supports only this type of biometrics. Make sure your face is enrolled.
2. In an app, create a biometric prompt with the "setConfirmationRequired" of the PromptInfo set to "true".
3. Successfully identify your face which enables the "Confirm" button.
4. Do NOT click the "Confirm" button.
5. Make a call to "cancelAuthentication" on the biometricPrompt (in the sample project we do this via a delayed runnable)
EXPECTED RESULTS
The biometric prompt dialog gets dismissed and the "onAuthenticationError" callback is called.
OBSERVED RESULTS
The biometric prompt dialog is not dismissed.
The "onAuthenticationError" callback is not called.
When no face has been identified yet (confirmation button disabled) or a wrong face has been identified and the confirmation button changes to "Try again" it works as expected.
NUMBER OF TIMES YOU WERE ABLE TO REPRODUCE:
10/10