Add a new test to debug multiple encryption keys working on iOS #441
Conversation
This file contains 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
|
I briefly looked into why the try catch wasn't able to catch it but couldn't figure it out. Hopefully this is just a testing issue. But let me know if you find that not to be the case. |
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.
Adding a new test for iOS that should pass but fails
It tries to recreate a second client with same inbox using another db encryption key
It's like the db was never encrypted to start with
NB: the thing that's supposed to throw in the try/catch does throw on Android (so that's good news!) but the try/catch doesn't seem to be able to catch it?