Expense - Not here page opens after moving IOU report to workspace

[jponikarchuk]

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: #85192
Email or phone of affected tester (no customers): sosjodijsodjoisjidojs@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Have at least one workspace.
• User has received IOU expense from another user.

1. Go to staging.new.expensify.com
2. Open 1:1 DM where IOU expense is received.
3. Open the expense.
4. Click More > Change workspace.
5. Select workspace.
6. Close the RHP.

Expected Result:

Central pane will change to 1:1 DM after moving IOU report to workspace.

Actual Result:

Central pane opens not here page after moving IOU report to workspace.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @aimane-chnaif

Issue Owner

Current Issue Owner: @aimane-chnaif

[melvin-bot]

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

[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: #85192 - "feat: deep link to report preview or message that caused GBR/RBR" by @aimane-chnaif (High confidence)
Related Issues: None

Recommendation: REVERT

PR #85192 should be reverted. This PR introduced deep linking to specific report actions when clicking LHN rows, which is causing navigation issues when moving IOU reports to workspaces.

Labels: Keeping DeployBlockerCash (this blocks the App deploy as it is a frontend bug affecting navigation)

📋 Detailed Analysis

Evidence

PR #85192 was merged on 2026-03-18 and introduced the ability to deep link to specific report actions from the LHN. The issue is reproducible on staging but NOT on production, which aligns with the PR having a production gate (isProduction check on line 76 of SidebarLinks.tsx that disables the feature in production).

The PR adds an actionTargetReportActionID parameter to navigation when clicking LHN rows, which changes the navigation behavior.

Verification

Files affected by the bug:

• /home/runner/_work/App/App/src/pages/ReportChangeWorkspacePage.tsx - Handles workspace change flow
• /home/runner/_work/App/App/src/pages/inbox/sidebar/SidebarLinks.tsx - Modified by PR feat: deep link to report preview or message that caused GBR/RBR #85192 to add deep linking

Confirmed PR #85192 modifies these areas:

• src/pages/inbox/sidebar/SidebarLinks.tsx (adds actionTargetReportActionID to navigation)
• src/libs/ReportUtils.ts (adds actionTargetReportActionID to OptionData type)
• src/libs/SidebarUtils.ts (propagates actionTargetReportActionID)
• src/components/LHNOptionsList/OptionRowLHNData.tsx (consumes actionTargetReportActionID)

Root Cause

When a user moves an IOU report from a 1:1 DM to a workspace:

1. User opens IOU expense from 1:1 DM
2. User clicks "More > Change workspace"
3. User selects a workspace
4. ReportChangeWorkspacePage.tsx calls Navigation.goBack(backTo) (line 89)
5. Simultaneously, moveIOUReportToPolicy changes the IOU report's chatReportID from the DM to the workspace expense chat (line 6211 of Report/index.ts)
6. The navigation attempts to return to the previous context, but the report has been moved to a different chat
7. This results in a "Not here" (FullPageNotFoundView) page being displayed

The PR #85192 introduced changes to the navigation flow that don't properly handle the case where a report's parent chat changes during the navigation sequence. The actionTargetReportActionID parameter adds complexity to the navigation that breaks when the underlying report structure changes.

Why it works in production but not staging: The PR author intentionally gated this feature with isProduction ? undefined : option.actionTargetReportActionID to prevent issues in production, which is why the bug only manifests on staging.

[aimane-chnaif]

The feature is only available in staging. We can demote this