Database not closing on Android

[vtenext-dan]

I was experiencing a problem on Android platform, when closing the database. This caused problems in my app, since in some cases I needed to reload the page, and to prevent opening the same database multiple times, before the reload I was closing the DB. Unfortunately this seemed not to work and in logcat I had:

sqlite returned: error code = 5, msg = database is locked, db=/data/data/[APP-ID]/databases/webview_db
sqlite returned: error code = 5, msg = database is locked, db=/data/data/[APP-ID]/databases/webview_db
CREATE TABLE android_metadata failed
Failed to open the database. closing it.
android.database.sqlite.SQLiteDatabaseLockedException: database is locked
... and so on ...

The issue seemed to be in the run() method of DBRunner:

dbrmap.remove(dbname); // (should) remove ourself

closeDatabaseNow(dbname);

Here, first the mapping with the db name is removed and then the database connection closed. But the closeDatabaseNow method uses that mapping to retrieve the database object, and since it has been removed, nothing is returned and the database is not closed.

The solution was simple: I just switched those rows and the database was closed correctly.

I hope this can help someone

[brody4hire]

+1 will make this fix sometime later thanks @magikozio

[brody4hire]

The fix has been published.

[brody4hire]

@durgaprasadp I am very sorry but this is not enough information to help you and from the log, I can see that you are using an old version of the plugin. Also, this issue was regarding a small fix that was needed in the past. The fix has been applied and this issue is now closed.

Please upgrade to use the latest version of this plugin. If you are still having problems, please do the following:

• Please make sure you are using the latest version. Older versions are normally not supported.
• Isolate the smallest test program that you can make to reproduce your problem
• Raise a new issue and post the entire test program where you see the issue.

[brody4hire]

@durgaprasadp can you try opening the database with androidDatabaseImplementation: 2 as described in README.md and try it again?