There's an intermittent bug recorded at #136 , wherein trying to use the app gives frequent "SqliteException(1032): while executing statement, attempt to write a readonly database". I think I've found the problem - the app creates directory /data/user/0/net.e1547/cache/e1547 , and starts putting cache files in there, but when the device memory (disk space) is low, the OS will frequently (like, every handful of seconds) clear the cache directory /data/user/0/net.e1547/cache , deleting the e1547 directory, and causing subsequent cache attempts to throw exceptions. Preferably, the app would detect this and either recreate the cache files whenever needed, or at least give the user a clear message explaining the situation. I actually had to free up more than ~2GB before the app started working again.
To Reproduce
- Fill your device memory with arbitrary files.
- Attempt to use the app (specifically, open the app, then click on several tags and expect errors.)
Expected behavior
Either the app recreates the cache repeatedly, or falls back to a different solution (in-memory cache?), or gives a useful error message.
Platform
- Device: Samsung Galaxy XCover Pro
- OS: Android
- Version 13
Logs
(I no longer have the logs or the error, but I posted my previous ones in #136 )
There's an intermittent bug recorded at #136 , wherein trying to use the app gives frequent "SqliteException(1032): while executing statement, attempt to write a readonly database". I think I've found the problem - the app creates directory /data/user/0/net.e1547/cache/e1547 , and starts putting cache files in there, but when the device memory (disk space) is low, the OS will frequently (like, every handful of seconds) clear the cache directory /data/user/0/net.e1547/cache , deleting the e1547 directory, and causing subsequent cache attempts to throw exceptions. Preferably, the app would detect this and either recreate the cache files whenever needed, or at least give the user a clear message explaining the situation. I actually had to free up more than ~2GB before the app started working again.
To Reproduce
Expected behavior
Either the app recreates the cache repeatedly, or falls back to a different solution (in-memory cache?), or gives a useful error message.
Platform
Logs
(I no longer have the logs or the error, but I posted my previous ones in #136 )