feat: don't stop with invalid key #1612
Merged
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.
An issue with the old sync was that if there was one record encrypted with a different key, sync would stop. You'd need to delete your account and start from scratch. This sucked.
This change means we will carry on, and try to encrypt and build with as much of the history as we are able to decrypt.
This is possible because we can quite happily store data on disk that we cannot decrypt. The old store couldn't do this.
In future, we might consider a keyring containing multiple keys.