[Due for payment 2025-11-12] Expense - Confirm page opens instead of Category after reset app & select a default workspace

[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.40-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: #72756
Email or phone of affected tester (no customers): sdpodskdskpsokmsop@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Have two non-default workspaces and no default workspace.
• Account has self DM.

1. Go to staging.new.expensify.com
2. Go to Account > Troubleshoot > Clear cache and restart > Reset and refresh.
3. Do not go to Inbox.
4. Open FAB > Create expense > Manual.
5. Enter amount > Next > Choose Self DM as recipient
6. On confirm page, click Category.
7. Select a workspace.

Expected Result:

Category page will open.

Actual Result:

Confirm page opens after selecting a default workspace.

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

Bug6987436_1761694001555.6.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @dylanexpensify

[melvin-bot]

Triggered auto assignment to @joekaufmanexpensify (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]

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

[melvin-bot]

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

[github-actions]

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

[parasharrajat]

I wouldn't say this is a deploy blocker. It is very unexpected for a user to follow these steps. As there is not data, user is redirected back. This is an edge case; we will work on it. cc: @cristipaval