Expense - After submitting expense to WS chat, submitting expense to user submits to WS chat

[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.1.53-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+sjdoidj12@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Create a workspace.
3. Go to workspace chat.
4. Submit an expense to workspace chat.
5. Open FAB > Create expense > Manual.
6. Enter amount > Next.
7. On confirmation page, click To field.
8. Select a user.
9. Submit the expense.

Expected Result:

The expense will be submitted to the selected user.

Actual Result:

The expense is submitted to the workspace chat.

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

Bug6844214_1748409916864.20250528_132315.mp4

View all open jobs on GitHub

[melvin-bot]

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

[robertjchen]

Looking for related PR

[BlameGPT]

Possible culprit PRs for this issue

• fix: app opens expense report instead of returning to confirm page after selecting a report #62351: The PR fixes navigation flow on the confirmation page when selecting a report, matching the issue's flow of selecting a user on the confirmation page before submitting an expense.
• Fix report selection #62659: This PR addresses report selection and editing on the confirmation page, which aligns with the issue's step of selecting a user (report) on the confirmation page before submitting.
• fix: scan expense encountered error when submit quickly #62189: This PR fixes errors encountered when submitting a scanned expense quickly from workspace chat, involving the confirmation step of expense submission.

Please 👍 or 👎