Scan - Admin can't pay a request with an empty merchant field

[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: v9.1.98-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-419/folder/13176933/41237714/856399141
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Device used: Mac 15.4.1 Safari, desktop, iPhone 13 iOS 18.6 Hybrid,Safari
App Component: Money Requests

Action Performed:

Precondition: Admin invited an employee to the workspace

1. Navigate to https://staging.new.expensify.com
2. As employee, start the submit expense flow > "Scan" receipt
   3.Upload a blurry receipt
   4.Complete the submit expense flow
   5.While the receipt is scanning - navigate to the request conversation
   6.Manually edit the amount field
   7.Verify the merchant field shows a error to "Enter a merchant"
   8.Navigate to the report conversation
   9.Verify the preview component has a red dot
   10.Navigate to the WS chat as the admin

Expected Result:

Admin can pay a request with an empty merchant field

Actual Result:

Admin can't pay a request with an empty merchant field

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

Bug6924924_1755964969944.Recording__506.mp4

View all open jobs on GitHub

[melvin-bot]

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

[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