Skip to content

[Due for payment 2025-12-08] Bank account - Browser back button reopens the same page after verifying with magic code #76192

Closed

Description

@mitarachim

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: 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:

  1. Go to staging.new.expensify.com
  2. Log in with a new Gmail account.
  3. Create a workspace.
  4. Go to workspace settings > Workflows.
  5. Click Add bank account.
  6. Update to USD if needed.
  7. Click Log into your bank.
  8. Enter magic code.
  9. Click browser back button or device back button.

Expected Result:

RHP will close.

Actual Result:

RHP reopens the same "Confirm currency and country" page.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug7014493_1764208331487.1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @VictoriaExpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Nov 27, 2025
  2. melvin-bot commented on Nov 27, 2025

    @melvin-bot

    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.

  3. github-actions commented on Nov 27, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  4. melvin-bot commented on Nov 27, 2025

    @melvin-bot

    Triggered auto assignment to @flodnv (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. melvin-bot commented on Nov 27, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  6. VictoriaExpensify commented on Nov 27, 2025

    @VictoriaExpensify
    Contributor

    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?

  7. 6 remaining items

  8. added and removed
    DeployBlockerIndicates it should block deploying the API
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 28, 2025
  9. mountiny commented on Nov 28, 2025

    @mountiny
    Contributor

    Fixed in staging, not a blocker anymore and we can close

  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 1, 2025
  11. 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
  12. melvin-bot commented on Dec 1, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  13. melvin-bot commented on Dec 1, 2025

    @melvin-bot

    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:

    • @jmusial does not require payment (Contractor)
  14. melvin-bot commented on Dec 1, 2025

    @melvin-bot

    @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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions