Closed m-natarajan closed 5 days ago
Triggered auto assignment to @bfitzexpensify (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
@bfitzexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Asked about the required account conditions for me to attempt to reproduce this here
@bfitzexpensify Eep! 4 days overdue now. Issues have feelings too...
Given Scott's comment in https://expensify.slack.com/archives/C07HPDRELLD/p1736887817936989, I am going to close this - doesn't seem like this was unexpected.
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: Reproducible in staging?: Reproducible in production?: If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: 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: @anmurali Slack conversation (hyperlinked to channel name): convert
Action Performed:
Expected Result:
With tryNewDot.classicRedirect.dismissed=false, the user should be automatically redirected to NewDot.
Actual Result:
The user remains on Expensify Classic, and redirection to NewDot does not occur.
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?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub