This repository was archived by the owner on Jun 20, 2023. It is now read-only.
Fixes 9002 error caused by test fragment risk reset (related to EXPOSUREAPP-1851) #1037
Conversation
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
…, but we don't delete the database itself. On app restart, there is a mismatch between the newly generated credentials and the old database.
jakobmoellerdev
previously approved these changes
Aug 18, 2020
The previous commit accidentally used the transitive dependency from google-utils.
|
Kudos, SonarCloud Quality Gate passed!
|
jakobmoellerdev
approved these changes
Aug 19, 2020
This was referenced Aug 21, 2020
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I came upon this while researching various avenues that could cause a 9002 error.
Resetting the preferences deletes our database encryption credentials, but we don't delete the database itself.
On app restart, there is a mismatch between the newly generated credentials and the old database.
I also annotated
resetInstanceas it should really only be used for testing (and currently only is).