Report - Empty report disappears after moving expense to a new report.

[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.3.7.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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-3293/folder/13176670/41237108/1143584610
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

1. Open the Expensify app.
2. Open any workspace chat.
3. Create a manual expense.
4. Open the just created expense.
5. Tap on report field and select "Create Report"
6. Once you land on empty report, tap on back button to return to chat.
7. Note that only expense in new report is visible. Empty report disappeared.
8. Return to "Inbox" and reopen chat.
9. Note that empty report reappears.

Expected Result:

Empty report should still be visible on chat after moving expense to a new report.

Actual Result:

Empty report disappears from chat after moving expense to a new report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7056004_1769122948385.Move.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @johncschuster (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 @aldo-expensify (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.

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #79415 - "Fix report field is enabled when there are no outstanding reports" by @bernhardoj (High confidence)
Related Issues: None identified

Recommendation: REVERT

PR #79415 introduced a new filtering mechanism for outstanding reports that appears to incorrectly handle empty reports after expenses are moved. The empty report temporarily disappears from the chat but reappears when navigating away and back, indicating a report visibility/filtering bug in the new useOutstandingReports hook logic.

Labels: Keeping DeployBlockerCash (this is a frontend bug requiring an App fix). Will remove DeployBlocker as this does not block the backend/Web deploy.

Detailed Analysis

Evidence

PR #79415 (merged 2026-01-22 at 16:03:21Z) introduced a new useOutstandingReports hook that replaced the previous outstanding reports filtering logic in MoneyRequestConfirmationListFooter.tsx and IOURequestEditReportCommon.tsx.

The bug reproduction steps exactly match the area modified by this PR:

• Creating an expense in workspace chat
• Using the report field to move expense to a new report
• The empty report visibility issue after moving the expense

Verification

The PR modified files directly related to report field functionality and outstanding report filtering:

• src/hooks/useOutstandingReports.ts (new file)
• src/components/MoneyRequestConfirmationListFooter.tsx
• src/pages/iou/request/step/IOURequestEditReportCommon.tsx
• src/pages/iou/request/step/IOURequestStepReport.tsx

The new hook calls getOutstandingReportsForUser → isReportOutstanding → !isArchivedReport(reportNameValuePair) which filters reports based on their archived status.

Root Cause

When an expense is moved from a report to a new report using the report field:

1. The original report becomes empty
2. The new useOutstandingReports hook filters outstanding reports
3. The empty report gets filtered out (likely temporarily marked as archived or its state changes)
4. The report disappears from the chat view
5. When navigating back to Inbox and reopening the chat, the report data refreshes and it reappears

The issue is that the new filtering logic in useOutstandingReports is too aggressive in filtering out empty reports that should still be visible in the chat, especially immediately after moving an expense to create a new report.