[Due for payment 2025-07-22] [Multi-Files Drag-and-Drop] Replace Receipts dropzone instead of Scan Receipts dropzone

[nlemma]

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.79-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: #65264
Email or phone of affected tester (no customers): -
Issue reported by: Applause Internal Team
Device used: MacOS 10.15.7
App Component: Chat Report View

Action Performed:

1. Create new Expense > Manual (for the workspace expense, do not approve it yet), in a workspace or DM you haven't created an expense in
2. Go to the money request view
3. Try to drag a file over the Report Screen

Expected Result:

Verify that Dual Dropzone is displayed.
Verify that you see Scan Receipts dropzone

Actual Result:

Verify that Dual Dropzone is displayed.
User see Replace Receipts dropzone

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

Bug6883465_1752141870999.Screen_Recording_2025-07-10_at_1.01.37_PM.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @joekaufmanexpensify

[melvin-bot]

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

[nlemma]

@joekaufmanexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.