[$250] Attachment- Corrupted PDF isn't triggering the error modal if sent with drag & drop

[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.74-2
Reproducible in staging?: Yes
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: #64323
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 10 / Chrome
App Component: Other

Action Performed:

1. Navigate to https://staging.new.expensify.com/
2. Log in with an expensifail account
3. Open any chat
4. Drag & drop a corrupted PDF along with some normal attachments to the "Add attachments" part of the chat

Expected Result:

Error modal should appear.

Actual Result:

Corrupted PDF isn't triggering the error modal if sent with drag & drop. Selecting the corrupted PDF along with normal attachments using the + - Att attachment flow triggers the modal.

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

Bug6875740_1751446770428!Corrupted_PDF.pdf

Bug6875740_1751446770424.bandicam_2025-07-02_10-53-13-062.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021941990584997280852
• Upwork Job ID: 1941990584997280852
• Last Price Increase: 2025-07-13

Issue Owner

Current Issue Owner: @s77rt

Issue Owner

Current Issue Owner: @koko57

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

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

[BlameGPT]

Possible culprit PRs for this issue

• Multi file attachments #64323: PR introduces new multi-file drag-and-drop handling and rewrites validateAttachment/useFileValidation; corrupted-file detection for drag-and-drop therefore depends on this new logic and is likely failing to raise the error modal for a bad PDF.
• Fix double modal hide callbacks when unmounted #64865: Touches BaseModal lifecycle; while less direct, any mis-timed hide callback could prevent the error modal from rendering, making it a secondary suspect.

If not above, check these

• MED Refactor ShowContextMenuContext to pass isReportArchived instead of rNVPs #65179: Changes to BaseAnchorForAttachmentsOnly and related attachment-rendering components could affect drag-and-drop attachment processing, preventing the corrupted-file validation that triggers the error modal.