Fixed
Status Update
No update yet.
Comments
jn...@google.com
st...@google.com
Would you like to move it to android.hardware.biometrics? It looks like the problem is deeper than androidx.
st...@google.com
ap...@google.com
Native Android 10 BiometricPrompt has exactly the same issue. If fixing this in the platform is impractical, maybe AndroidX Biometrics library can implement some workaround?
mk...@google.com
jo...@gmail.com
exxbrain@ can you attach a bugreport?
yi...@googlemail.com
I've created two sample projects (see attachment): one with android.hardware.biometrics (TestBiometricQ), other with androidx.biometric:biometric:1.0.0 (TestBiometricX).
They both have the same issue with setDeviceCredentialAllowed(true) (see #1).
Bug reports:
https://drive.google.com/file/d/1fx4EyHdfJ1koRIt2KZ1emQeRdSDnNOkG/view?usp=drive_web (biometric_q_report.zip)
https://drive.google.com/file/d/1PASxQhxXvLp62t91mYis28QhGqvHBfD5/view?usp=drive_web (biometric_x_report.zip)
On attached screenshots you can see "onAuthenticationError" toast alongside device pattern UI.
They both have the same issue with setDeviceCredentialAllowed(true) (see #1).
Bug reports:
On attached screenshots you can see "onAuthenticationError" toast alongside device pattern UI.
mk...@google.com
Some clarifications:
1. The issue applies to any non-biometric unlock method (pattern, PIN, or password), if fingerprint is configured too. Not sure about face recognition.
2. "onAuthenticationSucceeded" is not called after providing correct pattern/PIN/password.
1. The issue applies to any non-biometric unlock method (pattern, PIN, or password), if fingerprint is configured too. Not sure about face recognition.
2. "onAuthenticationSucceeded" is not called after providing correct pattern/PIN/password.
yi...@googlemail.com
There is no bug report - just inconsistent behavior. From my point of view Authentication shouldn’t be cancelled in the moment when user chooses “Use pin” in a biometric prompt.
mk...@google.com
Well, I would still call it a bug. Documentation for setDeviceCredentialAllowed() method says that user will be "given the option to authenticate with their device PIN, pattern, or password" - and this does not work: the user can enter PIN/password/pattern, but cannot authenticate, because the app always gets onAuthenticationError callback.
yi...@googlemail.com
Absolutely agree.
yi...@googlemail.com
Agree.
yi...@googlemail.com
Found another issue when setDeviceCredentialAllowed() is set to true.
I have attached video to show bug with bio-metric prompt.
BP is not removed when user does home button swipe while setDeviceCredentialAllowed() is set true.
I have attached video to show bug with bio-metric prompt.
BP is not removed when user does home button swipe while setDeviceCredentialAllowed() is set true.
st...@google.com
Do you want me to fix this issue?
Description
Component used: SwipeToDismissBox Version used: 1.0.0-alpha06 Devices/Android versions reproduced on:
Thehttps://developer.android.com/training/wearables/overlays/exit#horizontal-scroll
SwipeDismissFrameLayoutsolves this, and the problem is explained here:If this is already possible using thresholds or something in Compose, I'd be happy to see some documentation for this particular use case.