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
Wrong WS in To field when using scan option after user set second WS as default WS #72646
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 :
New user has atleast 2 workspaces
First WS is set as default WS
Launch Hybrid app or navigate to staging.new.expensify.com
Tap the scan option at the bottom right
Select Manual tab >> Enter amount >> Next (Note: To field set to default WS )
Go back to Workspace settings
Set the second WS as default WS (Tap 3 dots on non-default WS >> Set as default workspace)
Tap scan option at the bottom right above the navigation bar >> Manual tab >> Enter amount >> Next
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
👋 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.
Activity
melvin-bot commentedon Oct 15, 2025
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.melvin-bot commentedon Oct 15, 2025
Triggered auto assignment to @techievivek (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 15, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 15, 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:
VickyStash commentedon Oct 15, 2025
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue!
VickyStash commentedon Oct 15, 2025
Draft PR with a fix: #72701