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.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 83b8f6bfc46cf7e315a7bd3be1d758c99082211e
Author: Curtis Belmonte <curtislb@google.com>
Date: Wed Dec 11 17:12:56 2019

Ignore BiometricFragment error while launching CDC

Currently, BiometricFragment is receiving onAuthenticationError and
canceling authentication immediately while launching the confirm device
credential Settings activity. This commit fixes the issue by checking
the existing isConfirmingDeviceCredential bridge field before
propogating the error and cleaning up the prompt in BiometricFragment.

Test: support-biometric-demos app on various API 28 and 29 devices
Test: ./gradlew biometric:test
Test: ./gradlew biometric:connectedAndroidTest

Fixes: 143653944
Change-Id: I471e4de840e4d98c1a9121ec88558ca4654b0b2d

M biometric/src/main/java/androidx/biometric/BiometricFragment.java
M biometric/src/main/java/androidx/biometric/FingerprintHelperFragment.java
M biometric/src/main/java/androidx/biometric/Utils.java
M biometric/src/test/java/androidx/biometric/UtilsTest.java

https://android-review.googlesource.com/1187089

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

The following changes were cherrypicked through Coastguard (

https://android-build.googleplex.com/coastguard/)
Release Track: (

https://android-build.googleplex.com/coastguard/dashboard/5176090922385408/#/history/all)
Created: 2019-12-12 02:17:54.278918+00:00
Changes: aosp/1186804

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

The following changes were cherrypicked through Coastguard (

https://android-build.googleplex.com/coastguard/)
Release Track: (

https://android-build.googleplex.com/coastguard/dashboard/5176090922385408/#/history/all)
Created: 2019-12-13 19:22:25.444935+00:00
Changes: aosp/1189582

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

We're still seeing this faulty behaviour in version 1.0.1, is this issue truly fixed?

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

I don't think this issue is fixed, I am still facing it.

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

Issue is not fixed even on version 1.1.0

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."