IssueTracker

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build
Which Android build are you using? (e.g. OPP1.170223.012)

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)

Android bug report capturing (kindly share complete bugreport)
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.

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.

Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

Android build: N/A - firebase crashlytics doesn't provide that information. It happens on both Android 9 and Android 10.
Sample: N/A - it's a race condition can't reproduce it consistently
Frequency: ~1 %
Android bug report capturing:  N/A - firebase crashlytics doesn't provide that information

Problem:
In BiometricFragment the mBundle is not always set - so when isDeviceCredentialAllowed is called the mBundle.getBoolean(BiometricPrompt.KEY_ALLOW_DEVICE_CREDENTIAL, false) throws the NullPointerException.

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

commit 0b2dee89f68e9ed41c9552a93fee72364253af41
Author: Curtis Belmonte <curtislb@google.com>
Date:   Wed Nov 06 10:00:17 2019

    Fix possible NPE with BiometricFragment method
   
    The current implementation of
    BiometricFragment#setDeviceCredentialAllowed() tries to get a boolean
    from mBundle without first checking to see if mBundle is null,
    potentially resulting in a NullPointerException. This commit adds in the
    null check in order to make calling this method safer. It also adds a
    unit test case to exercise this behavior.
   
    Test: ./gradlew biometric:connectedAndroidTest
    Fixes: 142599311
    Change-Id: I18e03f926ff03c53f8cf1812fbad46ea75db6a32

M       biometric/src/androidTest/java/androidx/biometric/BiometricFragmentTest.java
M       biometric/src/main/java/androidx/biometric/BiometricFragment.java

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

  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/1159943
 

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

commit fd35a469cabd33509e1d90c57561e33be03a0dd8
Author: Sumir Kataria <sumir@google.com>
Date:   Tue Sep 18 13:11:51 2018

    Prevent potential foreign key constraints in AlarmMgr.
   
    This change is an addition to the one for JobScheduler:
    https://android-review.googlesource.com/c/platform/frameworks/support/+/758783
   
    Also, this change fixes a potential issue where handleScheduleWorkIntent
    was not being executed inside a transaction as it should.
   
    Bug: 114705286
    Test: Added and ran tests.
    Change-Id: Ica1e54e3e9d43d52e11731f3a5727433aac0f622

M       work/workmanager/src/androidTest/java/androidx/work/impl/background/systemalarm/SystemAlarmDispatcherTest.java
M       work/workmanager/src/main/java/androidx/work/impl/background/systemalarm/CommandHandler.java

https://android-review.googlesource.com/760504
https://goto.google.com/android-sha1/fd35a469cabd33509e1d90c57561e33be03a0dd8

Fixed in alpha09.

It is happening again on 2.7.1 version
 
`implementation 'androidx.work:work-runtime-ktx:2.7.1'

We have following gradle version, it is impacted heavily

Gradle: androidx.work:work-runtime:2.7.0@aar
Gradle: androidx.work:work-runtime-ktx:2.7.0@aar
Gradle: androidx.work:work-rxjava2:2.7.0@aar

Attachment: Impacted Users and session in a week
This issue has 16,025,903 crash events affecting 55,770 users

Stack Trace:

Fatal Exception: android.database.sqlite.SQLiteConstraintException: FOREIGN KEY constraint failed (code 787 SQLITE_CONSTRAINT_FOREIGNKEY)
       at android.database.sqlite.SQLiteConnection.nativeExecuteForChangedRowCount(SQLiteConnection.java)
       at android.database.sqlite.SQLiteConnection.executeForChangedRowCount(SQLiteConnection.java:890)
       at android.database.sqlite.SQLiteSession.executeForChangedRowCount(SQLiteSession.java:756)
       at android.database.sqlite.SQLiteStatement.executeUpdateDelete(SQLiteStatement.java:66)
       at android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:1920)
       at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1841)
       at androidx.sqlite.db.framework.FrameworkSQLiteDatabase.execSQL(FrameworkSQLiteDatabase.java:265)
       at androidx.work.impl.WorkDatabase$2.onOpen(WorkDatabase.java:167)
       at androidx.work.impl.WorkDatabase_Impl$1.onOpen(WorkDatabase_Impl.java:113)
       at androidx.room.RoomOpenHelper.onOpen(RoomOpenHelper.java:136)
       at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.onOpen(FrameworkSQLiteOpenHelper.java:201)
       at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:427)
       at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:316)
       at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.getWritableSupportDatabase(FrameworkSQLiteOpenHelper.java:151)
       at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper.getWritableDatabase(FrameworkSQLiteOpenHelper.java:112)
       at androidx.room.RoomDatabase.inTransaction(RoomDatabase.java:706)
       at androidx.room.RoomDatabase.assertNotSuspendingTransaction(RoomDatabase.java:483)
       at androidx.work.impl.model.WorkTagDao_Impl.getTagsForWorkSpecId(WorkTagDao_Impl.java:93)
       at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:135)
       at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at java.lang.Thread.run(Thread.java:923)

i met issue too:  FOREIGN KEY constraint failed (code 787 SQLITE_CONSTRAINT_FOREIGNKEY)