Automattic / Automattic/Automattic-Tracks-Android
android.database.sqlite.SQLiteReadOnlyDatabaseException
- Dominant language
- Kotlin
- Stars
- 31
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
From Fabric:
```
Fatal Exception: android.database.sqlite.SQLiteReadOnlyDatabaseException: attempt to write a readonly database (code 1032)
at android.database.sqlite.SQLiteConnection.nativeExecute(SQLiteConnection.java)
at android.database.sqlite.SQLiteConnection.execute(SQLiteConnection.java:555)
at android.database.sqlite.SQLiteSession.execute(SQLiteSession.java:619)
at android.database.sqlite.SQLiteStatement.execute(SQLiteStatement.java:44)
at com.automattic.android.tracks.datasets.EventTable.insertEvent(EventTable.java:102)
at com.automattic.android.tracks.TracksClient$1.run(TracksClient.java:117)
at java.lang.Thread.run(Thread.java:761)
```
**Source:** 5c4ef231f8b88c2963cb9e91
Contributor guide
No contributing guide indexed for this repository
Research direction
The report points to EventTable.insertEvent at line 102 and TracksClient$1.run at line 117; begin by reading those entry points and the referenced source commit 5c4ef231f8b88c2963cb9e91. Trace or reproduce the readonly-database path, then verify that event insertion no longer fails under the reported condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin, sqlite
- Domain
- databases, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100