fix: delay camera #76
Merged
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
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.
Currently there is a problem if you install the app for the first time:
The camera permission prompt is raised directly (and not only after you proceed to the next screen)
In the
layoutwe wait for the rootNavigationState before we do the redirect to circumvent a problem with redirects happening before the first render. So this means theConnectWalletscreen is rendered (but immediately replaced with the `Onboarding screen), which triggers the camera prompt.Now I introduced a newIndexroute, where we check for the onboarding status and redirect to the respective page.After many failed attempts this seems to be a solution that works reliably.Update: Refactored to another approach using a hook and removing the new index route