-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$500] Web - User It is not redirected to New dot after logging in in Old dot #31595
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01e4653540dbdcaa94 |
Triggered auto assignment to @jliexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
Is OldDot open source? Not sure this is something contributors can fix. |
@allroundexperts just going to assign you as @kbecciv is saying it's related to #31522 |
I'm also a bit confused by this issue's |
@jliexpensify Correct, user should be diredirected to ND as a UserB, updated the video! |
Bump @allroundexperts - might be related to your PR? |
@jliexpensify @kbecciv I just checked and the reason why you're not being redirected is that you don't have the redirect beta enabled for your account. In order to make sure that redirect happens, you need to be logged in to OldDot using an email that ends with |
I think this issue can be safely closed. |
Thanks for the context Sibtain! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.1.5
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR #31522
Action Performed:
Expected Result:
Actual Result:
User should directed to NewDot after sign with UserB in Olddot
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Recording.5480.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: