Expense - Missing Category and Reimbursable field after changing workspace

[lanitochka17]

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.97-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: #78758
Email or phone of affected tester (no customers): sdsoidjnosnjdsodsjno@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Create two workspaces.

Manual expense:

1. Go to staging.new.expensify.com
2. Open FAB > Create expense > Manual.
3. Enter amount > Next.
4. On confirm page, click To field.
5. Select another workspace.

Scan expense:

1. Go to staging.new.expensify.com
2. Open FAB > Create expense > Scan.
3. Upload a receipt.
4. On confirm page, click To field.
5. Select another workspace.

Distance expense:

1. Go to staging.new.expensify.com
2. Open FAB > Track distance > Manual.
3. Enter amount > Next.
4. On confirm page, click To field.
5. Select another workspace.

Expected Result:

Confirm page will not change after changing workspace.

Actual Result:

Category and Reimbursable field disappear after changing workspace.
For distance expense, Rate field changes to Pending.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7044724_1767983967656.1.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #78758

[melvin-bot]

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

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

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

[lanitochka17]

Production:

Recording.4695.mp4

[blimpich]

Confirmed locally that revert of #78758 fixes this. Beginning revert process.