Fix broken auth params when opening desktop App from deeplink. #189
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.
Fixes: Desktop - Open New Expensify - Web user is not automatically logged into the Desktop app Expensify#49539 (comment)
Explanation of Change
Huge help from @WojtekBoman on this one.
When we open desktop app from web deeplink, from a different user account, we go through the flow of logging current user out and redirecting to
LogInWithShortLivedAuthTokenPage.Because of resetting navigation after logout, we were always clearing route
params, but in this flow the authToken is in route params.Because of that once we navigated to
LogInWithShortLivedAuthTokenPage:This PR preserves params for everything but ReportSplit navigator.
Fixed Issues