IssueTracker

Hi, do you have a code sample that reproduces this problem?

Hi, we didn't get the time to reproduce this but this is happening in large numbers on alpha08. I thought this was fixed in alpha07. Fabrics link is also attached.

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

commit e6be41fdad08bb09c5f3ddb101bca0438773ca48
Author: Sumir Kataria <sumir@google.com>
Date:   Mon Sep 17 12:21:59 2018

    Prevent potential foreign key constraints.
   
    Scheduling happens in a separate DB transaction from making things
    as enqueued (for a variety of historical reasons that will soon be
    changing).  This allows for a race condition where a synchronous
    cancel/enqueue/enqueueUniqueWork can change the database and lead
    to a foreign key constraint violation because the original WorkSpec
    no longer exists.  This code handles that gracefully; we can
    remove it down the road when additional infrastructure and changes
    come online.
   
    Bug: 114705286
    Test: Added and ran tests.
    Change-Id: Id1c6cf48b305a3526e2913a38ee0b5398c244ba4

M       work/workmanager/src/androidTest/java/androidx/work/impl/background/systemjob/SystemJobSchedulerTest.java
M       work/workmanager/src/main/java/androidx/work/impl/background/systemjob/SystemJobScheduler.java

https://android-review.googlesource.com/758783
https://goto.google.com/android-sha1/e6be41fdad08bb09c5f3ddb101bca0438773ca48

A further fix should be available in alpha09.

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)