android.database.sqlite.SQLiteReadOnlyDatabaseException

Open

#1,373 opened on Jan 14, 2021 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language: Java
Stars: 11.1k
Forks: 2.2k
PR merge metrics: No merged PRs in 30d

Description

android.database.sqlite.SQLiteReadOnlyDatabaseException:
at android.database.sqlite.SQLiteConnection.nativeExecuteForChangedRowCount (Native Method)
at android.database.sqlite.SQLiteConnection.executeForChangedRowCount (SQLiteConnection.java:831)
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:1806)
at android.database.sqlite.SQLiteDatabase.execSQL (SQLiteDatabase.java:1733)
at com.liulishuo.filedownloader.database.SqliteDatabaseImpl.removeConnections (SqliteDatabaseImpl.java:120)
at com.liulishuo.filedownloader.database.RemitDatabase.syncCacheToDB (RemitDatabase.java:102)
at com.liulishuo.filedownloader.database.RemitDatabase.access$200 (RemitDatabase.java:39)
at com.liulishuo.filedownloader.database.RemitDatabase$1.handleMessage (RemitDatabase.java:76)
at android.os.Handler.dispatchMessage (Handler.java:103)
at android.os.Looper.loop (Looper.java:224)
at android.os.HandlerThread.run (HandlerThread.java:67)

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Start with the stack-trace entry points in com.liulishuo.filedownloader.database.SqliteDatabaseImpl.removeConnections and RemitDatabase.syncCacheToDB, then inspect how the Android SQLite database is opened and modified. Reproduce the read-only exception if possible and trace the relevant database state; done means the cause is identified, a verified fix or clear workaround is recorded, and regression coverage is added where the project supports it.

Written by the indexing model from the issue text.

Assessment

Tech stack: android, java, sqlite
Domain: database, mobile
Issue type: Bug
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 25/100