BIOMETRIC_ERROR_HW_NOT_PRESENT on Galaxy Tab A [170517889]

Fixed

Bug

Status Update

No update yet.

Description

ti...@gmail.com

created issue #1

Oct 10, 2020 10:37AM

BUILD INFO

Device type: Samsung Galaxy Tab A 2019
OS version: Android 10
Biometric library version: 1.1.0-beta01

STEPS TO REPRODUCE

Galaxy Tab A does not have any biometric sensor.
Setup a Pin/pattern/passcode etc.
Run the following code:

biometricPrompt.authenticate(BiometricPrompt.PromptInfo.Builder()
                    .setTitle("Some title")
                    .setDeviceCredentialAllowed(true) // or .setAllowedAuthenticators(Authenticators.DEVICE_CREDENTIAL or Authenticators.DEVICE_CREDENTIAL)
                    .build())

EXPECTED RESULTS

The keyguard activity should be displayed for user to enter pin/pattern/passcode.

OBSERVED RESULTS

Get error BIOMETRIC_ERROR_HW_NOT_PRESENT immediately in the callback.

NUMBER OF TIMES YOU WERE ABLE TO REPRODUCE (e.g. 3/10)

10/10

Comments

[Deleted User] <[Deleted User]> #2Oct 19, 2020 11:37PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Steps to reproduce
What steps are needed to reproduce this issue?

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Expected output
What is the expected output?

Current output
What is the current output?

Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.

Alternate method
After reproducing the issue, navigate to “developer settings”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

re...@gmail.com <re...@gmail.com> #3Nov 2, 2020 01:08PM

Steps to reproduce
1. Show the biomterics prompt
2. Use the wrong finger to authenticate several times in a row

Frequency
100% of the time

Expected output
The behavior is the same on all api levels

Current output
The behavior differs between api levels as described in the initial report/video

Android bug report capturing
There's no bugs to capture, this is a behavior difference, not a crash

Attached is a sample apk, all it does is show the biometric prompt using the lib

[Deleted User] <[Deleted User]> #4Jan 21, 2021 08:35PM

Attached bug reports

[Deleted User] <[Deleted User]> #5Jan 21, 2021 08:35PM

Issue is reproducible. More details are here -

https://drive.google.com/corp/drive/u/0/folders/1yJ1tnzJZvY_SQR-rXMI8qTOtb8sjyHkH (internal only link)

ah...@league.com <ah...@league.com> #6Jan 28, 2021 04:49PM

Oops, looks like this is related to

b/119597723

We need to support both of the cases

1) if the dialog is not showing or about to be shown, and there's lockout, we need to return the lockout error immediately
2) (this bug) if the dialog is showing, we want to delay a few seconds before dismissing the dialog / forwarding the result to the client

Josh do you have cycles to dig into this? I can't think of a clean solution right now but we can chat about it offline, maybe there's a simple way to fix this.

https://cs.corp.google.com/aosp-androidx/biometric/src/main/java/androidx/biometric/FingerprintHelperFragment.java?q=fingerprinthelperfragment.java+%22errMsgId+%3D%3D+BiometricPrompt.ERROR_LOCKOUT%22+file:%5Ebiometric/src/main/java/androidx/biometric/+package:%5Eaosp-androidx$&g=0&l=91

ah...@league.com <ah...@league.com> #7Jan 28, 2021 05:03PM

I'll try and get to this next week if that's okay.

wb...@gmail.com <wb...@gmail.com> #8Feb 19, 2021 12:57PM

3) Currently the FingerprintDialogFragment is shown regardless of lockout (which can result in a split second appearance), it's related to this bug and we should figure out a way to fix it as well.

wb...@gmail.com <wb...@gmail.com> #9Feb 19, 2021 04:45PM

aosp/929948 is merged, not sure why it didn't get closed here

wb...@gmail.com <wb...@gmail.com> #10Feb 23, 2021 11:22AM

A workaround is to use the deprecated keyguardManager.createConfirmDeviceCredentialIntent() in the authentication error callback when BIOMETRIC_ERROR_HW_NOT_PRESENT is returned

cu...@google.com <cu...@google.com> Mar 25, 2021 06:09PM

Reassigned to cu...@google.com.

[Deleted User] <[Deleted User]> #11Apr 6, 2021 01:28PM

This is sort of breaking the authentication flow. What will be the ETA for the fix?

cu...@google.com <cu...@google.com> #12Nov 17, 2021 05:40PM

This is fixed in version 1.2.0-alpha04 (releasing today).

kc...@google.com <kc...@google.com> Nov 17, 2021 06:29PM

Marked as fixed.

sa...@gmail.com <sa...@gmail.com> #13May 5, 2022 10:38AM

this is not fixed in 1.2.0-alpha04

ol...@gmail.com <ol...@gmail.com> #14Sep 20, 2022 09:55AM

Hi, is there any update here? Is this really fixed in `1.2.0-alpha04`? I faced with the same issue, but I wouldn't like to use alpha without being sure that the bug has been fixed.