Skip to content

Wrong WS in To field when using scan option after user set second WS as default WS #72646

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.31-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory around #72236
Email or phone of affected tester (no customers): kiatest.80+ck101425n@gmail.com
Issue reported by: Applause Internal Team
Device used: iPhone 16/iOS 18
App Component: Money Requests

Action Performed:

Precondition :

  1. New user has atleast 2 workspaces

  2. First WS is set as default WS

  3. Launch Hybrid app or navigate to staging.new.expensify.com

  4. Tap the scan option at the bottom right

  5. Select Manual tab >> Enter amount >> Next (Note: To field set to default WS )

  6. Go back to Workspace settings

  7. Set the second WS as default WS (Tap 3 dots on non-default WS >> Set as default workspace)

  8. Tap scan option at the bottom right above the navigation bar >> Manual tab >> Enter amount >> Next

  9. Observe incorrect WS (first WS) reflect in To field

Expected Result:

When user set 2nd WS as default one, the same one should reflect in To field in confirmation page.

Actual Result:

Wrong WS seen in To field when user set second workspace as default WS. First WS displayed in To field though user set second workspace as default one

Note : User has to refresh page or kill app for the correct default WS to show up in To field

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

Bug6975016_1760478194508.ScreenRecording_10-14-2025_17-40-40_1.mp4

View all open jobs on GitHub

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 Oct 15, 2025
  2. melvin-bot commented on Oct 15, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Oct 15, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 15, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 15, 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.
  6. VickyStash commented on Oct 15, 2025

    @VickyStash
    Contributor

    Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue!

  7. VickyStash commented on Oct 15, 2025

    @VickyStash
    Contributor

    Draft PR with a fix: #72701

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions