[Due for payment 2026-03-30] Attachment - "No content to add" error is shown when uploading attachment

[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.3.40-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #70740
Email or phone of affected tester (no customers): sdjsdjosijnsodiosd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.2 / Chrome
App Component: Chat Report View

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Upload an attachment.

Expected Result:

Attachment will be uploaded.

Actual Result:

"No content to add" error is shown when uploading attachment.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7106264_1773841586359.9.1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @parasharrajat

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #83299

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #83299 - "FAB popover decomposition" by @TMisiukiewicz (High confidence)
Related Issues: Duplicate of #85661

Recommendation: DUPLICATE

This issue is a duplicate of #85661. Both issues describe the identical bug with the same reproduction steps: "New report RHP opens and closes when creating second report."

The issue title mentions "Attachment - No content to add error" which appears to be incorrect. The actual bug described in the issue body matches #85661 exactly:

• Same version: 9.3.40-0
• Same PR reference: FAB popover decomposition #83299
• Same reproduction steps
• Same symptom: RHP opens and closes
• Same component: Reports > Create report

Labels: Keeping DeployBlockerCash since this is the same frontend bug as #85661, which is already being investigated and has a proposed fix.

📋 Detailed Analysis

Evidence

• Issue [Due for payment 2026-03-30] Attachment - "No content to add" error is shown when uploading attachment #85671 and [Due for payment 2026-03-30] Reports - New report RHP opens and closes when creating second report #85661 were both filed by @lanitochka17 on the same day
• Both reference PR FAB popover decomposition #83299 in the regression test link
• Both have identical reproduction steps (steps 1-9)
• Both show the same symptom: "New report RHP opens and closes"
• Both are reproducible in staging but NOT in production
• Both use the same test account email

Verification

This is clearly a duplicate issue. The causing PR #83299 has been verified in #85661, which includes:

• Detailed root cause analysis by @MelvinBot identifying the browser history race condition
• Proposed fix: Set shouldHandleNavigationBack: false in useCreateEmptyReportConfirmation.tsx
• Verification that the issue does not reproduce on main branch (only on staging)

Root Cause

Per the detailed analysis in #85661, the root cause is a browser history stack race condition introduced when PR #83299 migrated the empty-report confirmation from an inline <ConfirmModal> to the global modal system via useConfirmModal. The global modal system always sets shouldHandleNavigationBack: true, causing the FAB popover's deferred history.back() to inadvertently close the confirmation modal.

The fix is already being implemented in #85661.