You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Desktop - Login - Expired magic code for a code with no prior use + inability to exit screen #34585
Version Number: 1.4.25-7 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: Applause - Internal Team Slack conversation:
Action Performed:
Prerequisites: User must be logged into web app as User B
1 . Launch the Desktop app
Enter an email for a new account (USER A)
Go to the email inbox and locate the magic code
Copy the Magic link and modify it to staging
On the web, open a new tab and navigate to the staging magic link
Confirm that the user is prompted to open the desktop app
Click on the "Open app" option
Repeat steps 5,6 and 7
When the apps get opened, click on ''just sign in here ''button
ATTENTION >>>> After the first desktop launch using "Open app'' you'll need to clear browser data or open incognito mode and start the process from the prerequisites again (otherwise, the prompt to open the Desktop app will not be displayed!).
Expected Result:
The user should be able to sign in right after clicking on ''Just sign in here,'' and they should also have the option to exit the page
Actual Result:
When the desktop app is launched using the magic code deep link, the user encounters an expired magic code page even though the code is valid and has not been previously used. Additionally, it's impossible to exit that screen
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
I don't think this is that important, there is probably something strange with being logged in to one account then attempting to log in with a second account which new dot is not built to handle (same for old dot for that matter). closing this out.
Activity
github-actions commentedon Jan 16, 2024
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Jan 16, 2024
Triggered auto assignment to @bondydaa (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.bondydaa commentedon Jan 16, 2024
I don't think this is that important, there is probably something strange with being logged in to one account then attempting to log in with a second account which new dot is not built to handle (same for old dot for that matter). closing this out.