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
[Due for payment 2025-12-08] Bank account - Browser back button reopens the same page after verifying with magic code #76192
Version Number: 9.2.65-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#74481 Email or phone of affected tester (no customers):yonghongkok2+sdjoisdjno2@gmail.com Issue reported by: Applause Internal Team Device used: Mac 26.1 / Chrome App Component: Workspace Settings
Action Performed:
Go to staging.new.expensify.com
Log in with a new Gmail account.
Create a workspace.
Go to workspace settings > Workflows.
Click Add bank account.
Update to USD if needed.
Click Log into your bank.
Enter magic code.
Click browser back button or device back button.
Expected Result:
RHP will close.
Actual Result:
RHP reopens the same "Confirm currency and country" page.
👋 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'm not too sure what the culprit would be for this one.
I can't repro based on the steps given because I'm not asked for a magic code after clicking Log into your bank- this takes me directly to the banking connection:
2025-11-27_15-07-36.mp4
@mitarachim can you please check these repro steps?
changed the title [-]Bank account - Browser back button reopens the same page after verifying with magic code[/-][+][Due for payment 2025-12-08] Bank account - Browser back button reopens the same page after verifying with magic code[/+]on Dec 1, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.66-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@flodnv@VictoriaExpensify@jmusial The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Nov 27, 2025
Triggered auto assignment to @VictoriaExpensify (
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.github-actions commentedon Nov 27, 2025
👋 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 Nov 27, 2025
Triggered auto assignment to @flodnv (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 27, 2025
💬 A slack conversation has been started in #expensify-open-source
VictoriaExpensify commentedon Nov 27, 2025
I'm not too sure what the culprit would be for this one.
I can't repro based on the steps given because I'm not asked for a magic code after clicking
Log into your bank- this takes me directly to the banking connection:2025-11-27_15-07-36.mp4
@mitarachim can you please check these repro steps?
6 remaining items
mountiny commentedon Nov 28, 2025
Fixed in staging, not a blocker anymore and we can close
[-]Bank account - Browser back button reopens the same page after verifying with magic code[/-][+][Due for payment 2025-12-08] Bank account - Browser back button reopens the same page after verifying with magic code[/+]melvin-bot commentedon Dec 1, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 1, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.66-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-12-08. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Dec 1, 2025
@flodnv @VictoriaExpensify @jmusial The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]