Expense - Category is not auto-selected on confirm page when tracking distance

[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 self DM.
3. Click > Track distance > Manual.
4. Enter amount > Next.
5. On confirm page, Category field is empty.
6. Click Create expense.
7. Open the expense.
8. Category field is auto selected after creation but not on confirm page.

Expected Result:

On confirm page (Step 5), Category will be auto-selected.

Actual Result:

On confirm page (Step 5), Category field is not auto-selected.
Category is auto-selected after the expense is created.

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

Bug6987437_1761692122282.3.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @muttmuure (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 @mountiny (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.

[mitarachim]

Issue was found while executing QA for PR #72756