Wrong CryptoObject Type for canAuthenticate(int) Strong Authentication on API 29 [165824669]

Fixed

Bug

Status Update

No update yet.

Description

tb...@gmail.com

created issue #1

Aug 20, 2020 07:53PM

https://github.com/tylerbwong/BiometricCanAuthenticateBug

BUILD INFO

Device type: Samsung Galaxy S20 Ultra
OS version: 10
Biometric library version: 1.1.0-alpha02

STEPS TO REPRODUCE [Be as specific as possible please]

Call canAuthenticate(BIOMETRIC_STRONG)

EXPECTED RESULTS App should not crash

OBSERVED RESULTS App crashes with stack trace:

Caused by: java.lang.IllegalArgumentException: method android.hardware.biometrics.BiometricManager.canAuthenticate argument 1 has type android.hardware.biometrics.BiometricPrompt$CryptoObject, got androidx.biometric.BiometricPrompt$CryptoObject
        at java.lang.reflect.Method.invoke(Native Method)
        at androidx.biometric.BiometricManager.canAuthenticateWithStrongBiometricOnApi29(BiometricManager.java:412)
        at androidx.biometric.BiometricManager.canAuthenticateCompat(BiometricManager.java:381)
        at androidx.biometric.BiometricManager.canAuthenticate(BiometricManager.java:336)

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

Comments

cu...@google.com <cu...@google.com> Sep 14, 2020 09:21PM

Reassigned to cu...@google.com.

ap...@google.com <ap...@google.com> #2Sep 15, 2020 08:51PM

Marked as fixed.

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.

Issue 165824669

Description

Issue summary

Comments

cu...@google.com <cu...@google.com> Sep 14, 2020 09:21PM

ap...@google.com <ap...@google.com> #2Sep 15, 2020 08:51PM

Add comment

Issue metadata