[$350] Desktop - Scan - Amount field appears on confirmation page during scan expense flow

[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.0.20-4
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Launch New Expensify desktop app
2. Go to workspace chat
3. Open + > Submit expense > Scan
4. Upload a receipt
5. On confirmation page, exit the flow
6. Open + > Track expense > Scan
7. Upload a receipt
8. Note that Amount field appears on the confirmation page when it is a scan expense
9. Might need to repeat Step 3 to 7 until the result is Step 8

Expected Result:

Amount field will not appear on the confirmation page when it is a scan expense

Actual Result:

In Step 8, amount field appears on the confirmation page when it is a scan expense
This issue happens when exiting scan expense flow and then starting another scan expense flow (from submit scan to track scan or vice versa)

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

20240814_215349.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01c07e764c77ad212e
• Upwork Job ID: 1825632307909792212
• Last Price Increase: 2024-08-26

Issue Owner

Current Issue Owner: @fedirjh

[melvin-bot]

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

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

20240814_231923.mp4

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[roryabraham]

weird, but NAB