Fixed
Status Update
No update yet.
Comments
al...@google.com
se...@google.com
Would you like to move it to android.hardware.biometrics? It looks like the problem is deeper than androidx.
se...@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?
se...@google.com
exxbrain@ can you attach a bugreport?
se...@google.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.
se...@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.
se...@google.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.
ap...@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.
al...@google.com
Absolutely agree.
se...@google.com
bo...@googlemail.com
Agree.
al...@google.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.
dm...@gmail.com
Do you want me to fix this issue?
al...@google.com
It is still assigned to me.
ma...@gmail.com
Comment has been deleted.
Description
Component used: EditText Version used: Version 1.4.0-alpha02 Devices/Android versions reproduced on: Pixel 3a/4a/5
It seems that set the inputType over xml doesn't work anymore. I have attached a demo project where you can reproduce this issue. With Version 1.3.0 everything working fine.
Just simple things like:
are not working anymore. When you set it programmatically everything is working fine:
Also more critical things like 'textPassword' are not working correctly. The password doesn't show but the keyboard (in this sample gboard) is showing auto suggestions!. When you set the InputType programmatically auto suggestions got hidden.
I think it is a high priority thing because it is not immediately recognizable.