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
Precondition - User is NOT logged into Expensify in Safari
Open Slack Desktop app
Insert email for EXISTING account for login
Tap "Continue"
Open email app
Copy magic link
Paste magic link into Safari
Modify the link to staging
Press "Enter" to proceed with magic link
Click on "Just sign in here" text link.
Tap "Allow" in "Open "New Expensify" pop up
Expected Result:
User lands in expensify desktop app being logged in
Actual Result:
User lands in "Insert magic code" page with an error "Incorrect magic code". If user enters magic code from the same email after these steps - an error would still be displayed
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android / native
Android / Chrome
iOS / native
iOS / Safari
MacOS / Chrome / Safari
MacOS / Desktop
Version Number: 1.3.23-6
Reproducible in staging?: y Reproducible in production?: y 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 Notes/Photos/Videos: Any additional supporting documentation
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Precondition - User is NOT logged into Expensify in Safari
Expected Result:
User lands in expensify desktop app being logged in
Actual Result:
User lands in "Insert magic code" page with an error "Incorrect magic code". If user enters magic code from the same email after these steps - an error would still be displayed
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.23-6
Reproducible in staging?: y

Reproducible in production?: y
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
Notes/Photos/Videos: Any additional supporting documentation
Bug6078826_Recording__625.mp4
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @strepanier03