Repository navigation
fix(mob): stop the local database from becoming unreadable - #167
Merged
mrsumanbiswas merged 1 commit intoNov 7, 2026
Conversation
Concurrent first calls to DatabaseHelper.database each ran _initDB, so two random encryption keys could be generated and the stored one no longer matched the file. Share one initialisation future, and if an existing database still can't be opened, recreate it (Signal keys are regenerated and republished on sign-in) instead of failing forever. The inbox now shows a load error with a retry action instead of an empty "No conversations yet" state. Closes CommandLineCoding#159
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Concurrent first calls to DatabaseHelper.database each ran _initDB, so two random encryption keys could be generated and the stored one no longer matched the file. Share one initialisation future, and if an existing database still can't be opened, recreate it (Signal keys are regenerated and republished on sign-in) instead of failing forever.
The inbox now shows a load error with a retry action instead of an empty "No conversations yet" state.
Closes #159