You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Failed transaction commit can return a connection with an open native transaction to the pool #101
When an outer managed transaction's COMMIT fails, SQLCipher Android can release its connection to the pool while SQLite still has the native transaction open. A later operation using that connection can observe changes from the failed transaction even though the managed session reports that it is no longer in a transaction.
Reproduction
Using a fresh, file-backed SQLiteDatabase with foreign keys enabled:
The issue can also affect a subsequent operation on another thread when it acquires the same pooled connection. Observing the row on that connection does not establish that the failed commit was durable.
Expected behavior
After the commit failure, a connection returned for reuse should not still expose an unfinished transaction. The original failure should be reported, and the connection or pool should be made safe before reuse.
Thanks for bringing this to our attention, along with the pull request. We will investigate this further and reach back out when we have more to share.
Activity
developernotes commentedon Nov 4, 2026
Hello @virtanAnton,
Thanks for bringing this to our attention, along with the pull request. We will investigate this further and reach back out when we have more to share.