IssueTracker

Information redacted by Android Beta Feedback.

- Build Number: google/oriole/oriole:13/T3B3.230413.003/9957835:user/release-keys
  (Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)


New Bug report added.

Time around 10 AM IST the phone froze again and I had to restart again.

Debugging information
Google Play services
com.google.android.gms
Version 231613044 (23.16.13 (190400-527363516))
System App (Updated)

Android System WebView
com.google.android.webview
Version 561513534 (112.0.5615.135)
System App (Updated)

Network operator: airtel
SIM operator: airtel

Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

Issue is reproducible. More details are here - https://drive.google.com/open?id=1DoJlZ4WtmgbEPhH2HxNRsxLaG2MHL2b3  (internal only link)

I don't know what this is abou?

On Tue, Nov 5, 2019, 3:19 AM <buganizer-system@google.com> wrote:

This error case appears to be triggered by creating BiometricPrompt immediately before calling authenticate(), rather than recreating the prompt in the Activity's onCreate() (or Fragment's onCreateView()) lifecycle method as intended. That's obviously an easy mistake to make, so I'll work on making sure the documentation is clearer here.

The fact that the activity appears to hang afterward is definitely a bug and will be fixed by aosp/1151594, likely in a 1.0.1 bugfix release. For now, I'm closing this bug as a duplicate of b/143683687.

Correction: b/143091227

Must it be in onCreate?

I'm doing this in onResume instead of onCreate so that the prompt shows up when the user comes back to my app.

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

commit df08869e2c6f2d066f1caf143cebdb965c1b5a2c
Author: Curtis Belmonte <curtislb@google.com>
Date:   Mon Nov 18 15:17:00 2019

    Fix BiometricPrompt + device credential error case
   
    BiometricPrompt currently has a bug in the following usage scenario:
    1. The prompt is not instantiated in onCreate() or onCreateView()
    2. Device credential auth is enabled with setDeviceCredentialAllowed()
    3. authenticate() is called twice in the same activity/fragment
   
    When this happens, the handler bridge is incorrectly reset before the
    handler activity can be launched, preventing the prompt from being shown
    at all. While this isn't a recommended usage pattern for
    BiometricPrompt at the moment, it still shouldn't cause the prompt to
    get stuck in this state. This commit therefore ensures that the above
    scenario no longer triggers the bug.
   
    Test: Manually, using sample app from b/143097321
    Test: ./gradlew biometric:test
    Test: ./gradlew biometric:connectedAndroidTest
   
    Fixes: 143097321
    Change-Id: Ie7e343d9323437d9765e512a09a0e25a6c86dd8e

M       biometric/src/main/java/androidx/biometric/BiometricPrompt.java
M       biometric/src/main/java/androidx/biometric/DeviceCredentialHandlerActivity.java

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

Yes, initializing the prompt in onResume() should be fine as well.

Unmarked as duplicate, since aosp/1168851 should be a more proper fix for this. Targeting it for inclusion in 1.0.1.

  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-11-26 18:05:22.006209+00:00
  Changes: aosp/1168851
 

I believe I am facing a related issue. I am using BiometricPrompt with setDeviceCredentialAllowed. This is fully working on an older device running Oreo (now that I recreate the activity each time after using BiometricPrompt). The user can choose to use their fingerprint to authenticate, or can select to use the pin. In both cases, once the user successfully authenticates, onAuthenticationSucceeded is called on the BiometricPrompt.AuthenticationCallback.

However when used in the emulator, running Android 10, as soon as the user selects the "Use PIN" option, onAuthenticationError is called with errorCode=5 and errString=Authentication canceled

Yes I am facing the same issue. Once I get the errCode = 5, the activity starting acting very strange. It then again gives an errCode = 10 before crashing again.