Authentication callback not called when using password or fingerprint if setDeviceCredentialAllowed(true) and face recognition enabled [143653944]

Fixed

Bug

Status Update

No update yet.

Description

ma...@gmail.com

created issue #1

Oct 31, 2019 10:14PM

Hi, setDeviceCredentialAllowed(true) is causing some trouble if recognition enabled.
When I tap use password I get an error from the callback "Unknown error 10" and then when I enter my PIN code or fingerprint callback is not called.

BUILD INFO
- Device type: Samsung A50
- OS version: Android 9
- Biometric library version: "androidx.biometric:biometric:1.0.0-rc02"

STEPS TO REPRODUCE
1. Face recognition enabled, face registered and set as preferred biometric
2. Fingerprint registered and enabled (required to show face recognition prompt, see

https://issuetracker.google.com/issues/143695442)
3. PIN required to unlock device
4. setDeviceCredentialAllowed(true)
5. Face recognition prompt showing, tap use password
6. Enter PIN code or fingerprint (black screen in video)

EXPECTED RESULTS
Toast showing "Authentication successful" from callback method onAuthenticationSucceeded

OBSERVED RESULTS
Toast showing error at step 5 and callback not called when entering pin code or fingerprint

NUMBER OF TIMES YOU WERE ABLE TO REPRODUCE 100%

Thank you

MyApplication2.zip

14 MB

Download

scenario3.mov

5.4 MB

Download

Comments

ap...@google.com <ap...@google.com> #2Dec 12, 2019 02:16AM

Marked as fixed.

This would also be useful for entire types. Like switching from `android.support.v4.util.SparseArray` to `android.util.SparseArray`. The problem there, though, is that you have to remember to update the annotation value if SparseArray gets updated to include new functionality from newer API levels. That's a developer problem though.

an...@google.com <an...@google.com> #3Dec 12, 2019 02:18AM

Would be great to steal ReplaceWith from Kotlin's @Deprecated as well, although that isn't needed for an initial version.

an...@google.com <an...@google.com> #4Dec 13, 2019 07:23PM

I think @DeprecatedSdkVersion should accept an int array as there could be potentially more than one Deprecated Version.

[Deleted User] <[Deleted User]> #5Apr 21, 2020 01:21PM

For what case? Either you're below the version and in which case the method is used or you're equal to or above it in which case it's not needed.

[Deleted User] <[Deleted User]> #6Jul 8, 2020 06:29AM

This has now been implemented (the annotation name is @DeprecatedSinceApi).

Thanks for the suggestion!

ib...@gmail.com <ib...@gmail.com> #7Apr 25, 2022 07:07AM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Dolphin Canary 2 (2021.3.1.2)
Android Gradle Plugin 7.3.0-alpha02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

sa...@gmail.com <sa...@gmail.com> #8Nov 23, 2022 07:11AM

The issue still happens when we use a password/pin in version 1.2.0-alpha05.

sa...@gmail.com <sa...@gmail.com> #9Nov 23, 2022 07:46AM

The issue still happens when we use a password/pin in version 1.2.0-alpha05.
Condition: Turn ON the "Don't Keep Activities" option in the "Developer Options."