Fix incorrect 'device verified' screen when app was opened with no network connection #3110
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.
Type of change
Content
skipVerification
preference. I'd rather just remove it, but it's needed as a workaround onAppMigration02
.Motivation and context
It turns out
encryptionService.verificationState()
runs a network request that will cause a deadlock when it fails and that will trigger a timeout that will assume your session needs to be verified.Also fixed another deadlock that caused the screen to remain blank sometimes after logging in, because DataStore got stuck when checking the
skipVerification
state for some reason I don't fully understand. We'll have to keep an eye on similar behaviours through the app.Tests
Tested devices
Checklist