Added new option to isAvailable - requireStrongBiometrics #480
Conversation
This file contains 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
|
Let's do this in a major release since this could be a breaking change for some. |
NiklasMerz
approved these changes
Mar 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Added a new option to
isAvailable()-requireStrongBiometrics. Whentrue, backend calls toBiometricManager.canAuthenticate()will specify strong biometrics only. This should fix the underlying issue behind #473.How did you test your changes?
Tested on Android Samsung Galaxy S22. Confirmed that
isAvailable(successFN, errorFN, { requireStrongBiometrics: true })fails when the device has only a face ID (weak) registered and passes when a device has one or more fingerprints (strong) registered.