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

Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.

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

Great! Thanks a lot, I'll look for the live updates soon!

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

This also seems to happen on Lenovo TB-X505F Android 10 tablet

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

any ETA for a fix?

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

Seeing this on a SM-T510 running Android 10

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

in versions 1.0.1 and 1.1.0

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

also happens with 1.2.0-alpha02

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

seems to be due too hasBiometrics() return false:

if (BiometricManager.hasBiometrics(mContext)) {
mService.authenticate(mToken, sessionId, userId, mBiometricServiceReceiver,
mContext.getOpPackageName(), mBundle, confirmDeviceCredentialCallback);
} else {
mExecutor.execute(() -> {
callback.onAuthenticationError(BiometricPrompt.BIOMETRIC_ERROR_HW_NOT_PRESENT,
mContext.getString(R.string.biometric_error_hw_unavailable));
});
}

in android.hardware.biometrics.BiometricPrompt

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.