Fixed
Status Update
Comments
ph...@monzo.com <ph...@monzo.com> #2
This happens to me when using pattern+fingerprint on api 29 using 1.0.1
cu...@google.com <cu...@google.com>
cu...@google.com <cu...@google.com>
ph...@monzo.com <ph...@monzo.com> #4
Is there any workaround for this? Can we expect this to be fixed?
[Deleted User] <[Deleted User]> #5
I am facing the same problem too! Is there any solution to this problem?
re...@infinum.com <re...@infinum.com> #6
Still seeing this issue on Android 10 Pixel 4.
re...@infinum.com <re...@infinum.com> #7
Our team is facing this issue as well. What are the alternatives available right now apart from cloning the library and changing the behavior?
Description
On an API 29 Pixel 4
androidx.biometric.BiometricManager#canAuthenticate(Authenticators.BIOMETRIC_STRONG)
returnsBIOMETRIC_STATUS_UNKNOWN
. I believe this is because thecanAuthenticate(CryptoObject)
method only works on Samsung devices - as far as I can tell it has never existed in AOSP.Some possible solutions (there may well be reasons not to do these things):
assume_strong_biometrics_prefixes
array, which is currently empty. Devices with fingerprint should be OK because they fall back tocanAuthenticateWithFingerprintOrUnknown()
, but I haven't actually tested this.setUserAuthenticationValidityDurationSeconds(-1)
) inAndroidKeyStore
, which fails with the following exception if the user doesn't have strong biometrics available & enrolled (I don't know if this is reliable across OEMs and API versions):BUILD INFO
STEPS TO REPRODUCE
androidx.biometric.BiometricManager#canAuthenticate(Authenticators.BIOMETRIC_STRONG)
EXPECTED RESULTS
Receive
BIOMETRIC_SUCCESS
.OBSERVED RESULTS
Receive
BIOMETRIC_STATUS_UNKNOWN
.NUMBER OF TIMES YOU WERE ABLE TO REPRODUCE (e.g. 3/10)
10/10