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.

Hi Josh, friendly ping for an update on progress

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

i think the TL;DR is that this is stuck behind investigating the current lab outages, which are more urgent.

pending CL is https://android-review.googlesource.com/c/platform/system/core/+/1250677.

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

Have you consider snappy or zstd? From my experience snappy compresses at around 200~300MB/s with reasonable compression rate ~30%.

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

For brotli, try quality level 1, this can give around 150-200MB/s with a much better compression ration than snappy of over 60%. Brotli quality 0 is even faster for still over 50% compression.

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

Hmm, gerrit-watcher didn't post the CLs on this bug, so I guess I'll do so manually:

https://android.googlesource.com/platform/system/core/+/939fc19aee7f6a19ce0f4fa91557bbbe9cd974f5 added brotli support (with quality level 1)

https://android.googlesource.com/platform/system/core/+/ec44d35fde60d20d9ab1c6fb9ac7ee844335f1eb added LZ4

Throughput numbers from a device:

           none    brotli    lz4
USB 3.0     120       110    190
USB 2.0      38        75     63

I'm seeing identical throughput with brotli quality 0 and 1 (110MB/s end to end), although there's some giant low hanging fruit to compress multiple files at once.

zstd isn't in the tree yet (I started the ball rolling on that, but no idea when it'll end up getting merged), but I'll take a look at it eventually, probably when I get around to implementing compression for generic streams in adb (b/153901735).

This is probably good enough to call this fixed for now.

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