Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"SQLiteException: Database is locked" error is still occuring #8382

Open
wrdhub opened this issue Jan 27, 2025 · 3 comments · Fixed by #8412
Open

"SQLiteException: Database is locked" error is still occuring #8382

wrdhub opened this issue Jan 27, 2025 · 3 comments · Fixed by #8412
Labels
android issues that concern the android client but not all clients bug broken functionality, usability problems, unexpected errors
Milestone
264.250130.1

Comments

@wrdhub
Copy link
Contributor

wrdhub commented Jan 27, 2025

The solution associated with #8049 was not a bug fix, as we could not reproduce the error, but a band-aid to hopefully catch the error. This error still occurs even with that band-aid.

I am now able to more reliably produce this error so we can hopefully find a better fix:

Repro steps:

  1. Log into android app and leave open on Inbox with notifications enabled
  2. Log into the same account on desktop, but do not leave open (but still able to receive notifications
  3. Send mail to account
  4. Error will occur on android app sometimes

Notes:
step 2 may not be necessary
@wrdhub wrdhub added android issues that concern the android client but not all clients bug broken functionality, usability problems, unexpected errors labels Jan 27, 2025
@wrdhub wrdhub changed the title SQLiteException: Database is locked is still occuring "SQLiteException: Database is locked" error is still occuring Jan 27, 2025
@BijinDev BijinDev self-assigned this Jan 28, 2025
@BijinDev
Copy link
Contributor

Removing ""openedDb.query("PRAGMA busy_timeout = 100")" get rid of this scenario, which we added to avoid database locked issue.

@charlag
Copy link
Contributor

charlag commented Jan 28, 2025

That's odd. Should we try a longer one?

BijinDev added a commit that referenced this issue Jan 28, 2025
@BijinDev
Fix "SQLiteException issue in Android"
32b06c5 
Fixed by changing busy_timeout from 100 to 1000

close: #8382
@BijinDev BijinDev mentioned this issue Jan 28, 2025
Closed
BijinDev added a commit that referenced this issue Jan 28, 2025
@BijinDev
Fix "SQLiteException issue in Android"
5dc6f35 
Fixed by changing busy_timeout from 100 to 1000

close: #8382
@BijinDev BijinDev mentioned this issue Jan 28, 2025
Merged
@BijinDev BijinDev linked a pull request Jan 28, 2025 that will close this issue
Fix "SQLiteException issue in Android" #8412
Merged
@hrb-hub hrb-hub added this to the Mailbox Export milestone Jan 29, 2025
@wrdhub wrdhub added the state:tested We tested it and are about to release it label Jan 29, 2025
@BijinDev BijinDev removed the state:tested We tested it and are about to release it label Feb 4, 2025
@BijinDev
Copy link
Contributor

BijinDev commented Feb 4, 2025 •
edited
Loading

Maybe handling migration from sqlcypher3 to sqlcypher4 will fix this
https://discuss.zetetic.net/t/upgrading-to-sqlcipher-4/3283

Notes
Need to find a scenario to reproduce this issue.

@BijinDev BijinDev reopened this Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
android issues that concern the android client but not all clients bug broken functionality, usability problems, unexpected errors
Projects
None yet
Milestone
264.250130.1
Development

Successfully merging a pull request may close this issue.

Fix "SQLiteException issue in Android" tutao/tutanota
4 participants
@charlag @wrdhub @hrb-hub @BijinDev