IssueTracker

Is there any updates? This is a big problem!

Hi there - could you provide more context on the issue & a sample project to reproduce? Database locked exceptions are quite difficult to pinpoint without a repro project. Thanks!

Hi. It is reproduceable on some users by using this code:

suspend fun <R> MyDatabase.workaroundWithTransaction(block: suspend TransactionScope<R>.() -> R) {
    useWriterConnection {
        it.immediateTransaction(block)
    }

    // TODO: Temporally fix https://issuetracker.google.com/issues/340606803#comment2
    // Manually triggers invalidation
    invalidationTracker.refreshAsync()
}

Maybe it is about this? https://android-review.googlesource.com/c/platform/frameworks/support/+/3114928

I am not sure.

Hi. Please merge the pull request. This is big problem!

Hi. Is there any updates on this problem?

Hi, I updated my version to alpha12 but still have these crashes. Please release a fix asap.

Will there be fixes released this Wednesday?

Hey, there is no release on Wednesday (holiday in the USA)

We haven't found the root cause of this exception, it happens when SQLite can't commit the transaction because some other connection has a lock, we need more information, a sample project that reproduces the issue preferably, or more details on how the database is being used (is it from multiple process? is there heavy concurrency?).

You can also increase the time SQLite will wait before it error with 'database locked' by executing PRAGMA busy_timeout = <time in ms>, the current default is 3000

Thank you for you response.

1. Isn't these pull request addressed this issue? 1.1 https://android-review.googlesource.com/c/platform/frameworks/support/+/3408679 1.2 https://android-review.googlesource.com/c/platform/frameworks/support/+/3114928
2. According to RoomDB documentation about withTransaction: "Room will only perform at most one transaction at a time, additional transactions are queued and executed on a first come, first serve order." So the transaction should just wait for other transaction to complete and not throw exception instead. Isn't it?