[Due for payment 2026-08-05] Report - Expense deleted offline can still be opened and leads to "It´s not here" RHP.

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.45-0
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 BrowserStack: #92546
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

1. Open the staging.new.expensify.com website.
2. Navigate to workspace chat.
3. Create two manual expenses.
4. Open the report of the just created expenses.
5. Turn off internet connection.
6. Select and delete one of the expenses.
7. Return to chat.
8. Click above the deleted expense preview.
9. Note that report opens and a RHP with "It´s not here" message appears.

Expected Result:

User shouldn´t be able to open the report of a deleted expense.

Actual Result:

Expense deleted on a report with more than one expense, can still be opened and leads to a "It´s not here" RHP.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7219098_1785179354231.Deleted_RHP.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7219098

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/4635cb1bf881057e270242d529f7221b60f32754c102a90c76b7ffc11226335d

[melvin-bot]

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

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

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #92546 - "Navigate to the clicked expense in a multi-expense report preview" by @wildan-m (High confidence)
Related Issues: #91042 (the feature request PR #92546 implemented)

Recommendation: REVERT

PR #92546 changed each expense card in the multi-expense report preview to navigate to that specific expense's thread; an expense deleted offline is intentionally kept in the carousel while offline, so tapping its (now dead) thread lands on the "It's not here" RHP. A targeted fix is possible (below), but a clean revert restores the prior safe behavior where every card opened the parent report.

Assigned: @wildan-m (PR author), @jayeshmangwani and @MonilBhavsar (approving reviewers)
Labels: No change — DeployBlockerCash is kept because this is an App-side bug that blocks the App deploy. (DeployBlockerCash was added by applause-bot automation, not an internal employee.) There is no DeployBlocker label on this issue.

📋 Detailed Analysis

Evidence

• The bug's flow is "click above the deleted expense preview" in a workspace chat's multi-expense report preview carousel. PR Navigate to the clicked expense in a multi-expense report preview #92546 is precisely the PR that rewired that carousel: before it, every card called the report-level openReportFromPreview handler; after it, each card opens its own expense via a new openTransactionFromPreview(item) handler.
• PR Navigate to the clicked expense in a multi-expense report preview #92546 modifies src/components/ReportActionItem/MoneyRequestReportPreview/index.tsx — the exact component that renders the preview carousel and its per-card press handler.
• Merge date aligns: PR Navigate to the clicked expense in a multi-expense report preview #92546 merged 2026-07-27 (item Add Android app icon #74 in the 9.4.45-0 StagingDeployCash checklist Deploy Checklist: New Expensify 2026-07-27 #97134) and the blocker was reported the same day. The issue notes this is a new feature that does not exist in production — consistent with a staging-only regression introduced by a PR in this release.
• Before this PR, tapping any card (including a card for an expense deleted offline) opened the parent report, so there was no "not found" screen. The regression is the new per-expense navigation.

Verification

Affected file (merged at fd93ec969b04d4d78a4956bf87b06c60d6dc19ff):

• src/components/ReportActionItem/MoneyRequestReportPreview/index.tsx

Confirmed PR #92546 touches this file (files changed):

• src/components/ReportActionItem/MoneyRequestReportPreview/index.tsx
• src/components/ReportActionItem/MoneyRequestReportPreview/ReportPreviewActionButton.tsx
• src/libs/Navigation/Navigation.ts
• test files

Root Cause

1. When offline, deleted transactions are intentionally kept in the rendered carousel so the preview stays consistent offline:
   index.tsx#L84-L85

   const allReportTransactions = Object.values(reportTransactionsCollection ?? {}).filter((transaction): transaction is Transaction => !!transaction);
   const transactions = allReportTransactions.filter((transaction) => isOffline || transaction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE);

   So while offline the deleted expense's card is still shown and remains pressable.

2. Each card's press now calls the new per-expense handler:
   index.tsx#L355 — onPreviewPressed={() => openTransactionFromPreview(item)}

3. openTransactionFromPreview only short-circuits to the parent report when transactions.length <= 1. With two expenses (minus one deleted, but still counted because the offline filter keeps it), the count is still 2, so the guard is skipped and it resolves + navigates to the deleted expense's thread:
   index.tsx#L281-L314

   if (transactions.length <= 1) {
       openReportFromPreview();
       return;
   }
   const childReportID = resolveChildReportID(transaction);
   if (childReportID) {
       navigateToExpense(childReportID); // navigates to the deleted (now non-existent) expense thread
       return;
   }

4. resolveChildReportID returns/creates a thread id for the deleted transaction and navigates to it; because the expense has been deleted, the thread renders the "It's not here" not-found RHP.

Suggested fix (if ROLL FORWARD is preferred over revert)

Deleted-but-optimistically-present transactions should not deep-link to their own expense thread. Either:

• In openTransactionFromPreview, treat a transaction whose pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE like the single-expense case and fall back to openReportFromPreview(); or
• Disable / suppress the press on cards for transactions pending deletion.