Database journal mode changed errors about stetho

[jasta]

The issue, I believe, is that we open the database handle ourselves rather than trying to re-use an existing connection which means that the current process may have already opened the database using different flags. Attempting to re-open it may reconfigure details like write-ahead logging, which cannot be done while the database is locked.

For this to work, I think we'd need some way of detecting the correct configuration and applying it, but I'm not extremely familiar with this problem space and would need to investigate much deeper. Maybe it works to just check for a -wal file? :)

[Tolriq]

Well this sounds more complex indeed and in the end is not error prone due to concurrency issues :(

I suppose locks would prevents database corruption and just throws errors in Stetho.

Maybe for applications that needs to keep database opens add a callback in the instance builder to ask the application for the SQLiteConnection or whatever Stetho needs on target database ?

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

[jasta]

Any chance we can get a PR to fix this? I don't have time to investigate further personally and want to tidy up the issues list.

[Tolriq]

Well sorry but this is a little out of my competences to do this right :(

[jasta]

We addressed it with an extensibility layer; closing to clean up issues.