Expense - Next button on recipient list opens scan first page after changing recipient

[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.16-0
Reproducible in staging?: Y
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 TestRail: #68631
Email or phone of affected tester (no customers): jdsonijsojdoisjisojd@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• Account does not have any workspace

1. Go to staging.new.expensify.com
2. Open 1:1 DM with any user and send a message (we will need this user later)
3. Open FAB > Create expense > Scan
4. Add a receipt
5. Enter email that you don't have chat with and select the user
6. On confirm page, click To field
7. Select the user from Step 2
8. On confirm page, click RHP back button
9. On recipient page, click Next button (IMPORTANT)

Expected Result:

App will proceed to confirm page

Actual Result:

App opens scan first page

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6950916_1758393772380.Screen_Recording_2025-09-21_at_02.31.14.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 @stitesExpensify (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.

[stitesExpensify]

@BlameGPT