Fatal Exception: android.database.sqlite.SQLiteConstraintException FOREIGN KEY constraint failed (code 787) [114705286]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Sep 10, 2018 07:08PM

Component used:WorkManager
Version used:1.0.0-alpha08
Devices reproduced on:Xiaomi, Motorola, Samsung, Oppo, etc
Android versions reproduced on:6,7,8,9

We are facing this crash with 2 stack traces :

android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId (SQLiteConnection.java)
android.database.sqlite.SQLiteConnection.executeForLastInsertedRowId (SQLiteConnection.java:812)
android.database.sqlite.SQLiteSession.executeForLastInsertedRowId (SQLiteSession.java:788)
android.database.sqlite.SQLiteStatement.executeInsert (SQLiteStatement.java:86)
android.arch.persistence.db.framework.FrameworkSQLiteStatement.executeInsert (SourceFile:50)
android.arch.persistence.room.EntityInsertionAdapter.bind (SourceFile:64)
androidx.work.impl.model.SystemIdInfoDao_Impl.insertSystemIdInfo (SourceFile:52)
androidx.work.impl.background.systemjob.SystemJobScheduler.schedule (SourceFile:92)
androidx.work.impl.Schedulers.schedule (SourceFile:99)
androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground (SourceFile:114)
androidx.work.impl.utils.EnqueueRunnable.run (SourceFile:86)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1113)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:588)
java.lang.Thread.run (Thread.java:818)

android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId (SQLiteConnection.java)
android.database.sqlite.SQLiteConnection.executeForLastInsertedRowId (SQLiteConnection.java:812)
android.database.sqlite.SQLiteSession.executeForLastInsertedRowId (SQLiteSession.java:788)
android.database.sqlite.SQLiteStatement.executeInsert (SQLiteStatement.java:86)
android.arch.persistence.db.framework.FrameworkSQLiteStatement.executeInsert (SourceFile:50)
android.arch.persistence.room.EntityInsertionAdapter.bind (SourceFile:64)
androidx.work.impl.model.SystemIdInfoDao_Impl.insertSystemIdInfo (SourceFile:52)
androidx.work.impl.background.systemjob.SystemJobScheduler.schedule (SourceFile:92)
androidx.work.impl.Schedulers.schedule (SourceFile:99)
androidx.work.impl.WorkManagerImpl.rescheduleEligibleWork (SourceFile:555)
androidx.work.impl.utils.ForceStopRunnable.run (SourceFile:74)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1113)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:588)
java.lang.Thread.run (Thread.java:818)

Here is the fabrics link for this crash:

http://crashes.to/s/50397ac3f50

Comments

su...@google.com <su...@google.com> #2Sep 17, 2018 06:17PM

This is a hard one. We can't easily read native crashes from that Motorola device since their system image is not public. I assume you can't reproduce this either, but if possible can you try using WorkManager 2.0.0 or 1.0.1-rc01? This would help track down the possible changes that might have introduced this issue. Thanks!

[Deleted User] <[Deleted User]> #3Sep 17, 2018 06:30PM

We actually did reproduce it, the current store version of Pocket Casts has WorkManager 2.0.0 and this bug if you want to try and test something. I will try 1.0.1-rc01 and report back.

ap...@google.com <ap...@google.com> #4Sep 17, 2018 09:29PM

Is there a difference between 1.0.1 and 2.0.1? We tried 2.0.1 and it was crashing, if there is a difference I can try 1.0.1 but I thought they were the same?

su...@google.com <su...@google.com> #5Sep 17, 2018 09:29PM

Can you also describe how you trigger the bug and which devices manifest the problem? Is it just running the app? Is it doing something specific?

ap...@google.com <ap...@google.com> #6Sep 18, 2018 09:28PM

We are testing on a Moto X running Android 6.0 but our play store report shows numerous motorola devices are crashing as the attached screenshots show. We just downloaded a bunch of episodes (which uses workmanager) and eventually it started crashing, it would then crash at start up every time.

su...@google.com <su...@google.com> #7Sep 25, 2018 08:02PM

Marked as fixed, reassigned to su...@google.com.

So to answer your earlier question, 1.0.1 should be equivalent but I think there may be some small differences in Room between 1.0 and 2.0 and since this crash seems related to Room, that's why we were asking if you could check to see if you can reproduce it on 1.x.

Regarding the initial crash, do you have any logs for that?

ak...@gmail.com <ak...@gmail.com> #8Dec 1, 2022 06:41PM

This is the log I have. Hope it helps. Will test 1.0.1 for you

mw...@gmail.com <mw...@gmail.com> #9Apr 21, 2023 09:31AM

The logs are too short its just the crash and not much else before. :(

If the phone happens to be rooted and you are OK with sharing DB queries then you can enable SQL logging so we can see the queries that are occurring:
adb shell setprop log.tag.SQLiteStatements VERBOSE
adb shell stop
adb shell start

It would also be great if you can send us a bigger set of logs, or even better yet a bugreport after the crash occurs. (

https://developer.android.com/studio/debug/bug-report)

Fri Apr 21 2023 14:59:31 GMT+0530 (India Standard Time).png

198 KB

View

Download

xu...@gmail.com <xu...@gmail.com> #10Jul 10, 2023 03:23AM

We can't root the phone sorry, we might be able to send a bug report though