Skip unneeded confirmation button when using passive biometrics such as face unlock #174
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #162.
As explained in the Android docs, low-risk actions (such as logging into an app) should not require an explicit action by the user when using a passive biometric authentication method, such as the secure face unlock used by newer Pixel phones. This is only meant for high-risk operations such as purchases.
Unfortunately, the Biometrics API defaults to
truefor this, which makes the experience unnecessarily cumbersome. To fix it, we just need to pass the.setConfirmationRequired(false)flag to the biometric prompt builder, which will make the authentication experience much smoother, just like it is on iPhones.Submitting this super simple PR in hopes of getting this moving, as I see the issue has remained unaddressed for some time now ;-)