[Due for payment 2026-10-30] Pay someone - Expense details RHP closes after opening it from table view

@daledah

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

Version Number: 9.5.5-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: #103121
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Go to staging.new.expensify.com
Go to 1:1 DM with any user.
Click + > Pay.
Complete the flow to pay the user.
Open the report.
Click More > Switch to table view.
Click on the expense row.

Expected Result:

Expense details RHP will not close.

Actual Result:

Expense details RHP closes after opening it from table view.

On Android, it shows not here page briefly then it closes and returns to table view.

Workaround:

Unknown

Platforms:

Screenshots/Videos

Bug7280507_1791405156173.6.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7280507

Issue Owner

Current Issue Owner: @daledah

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

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

@Beamanator

@Beamanator @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #103121

💬 A slack conversation has been started in #expensify-open-source

👋 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:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Deploy Blocker Investigation

Cause: Add a More menu option to switch single-expense reports between expense view and table view (Expensify/App#103121). Confidence is high. This is a frontend bug, so DeployBlockerCash is correct.

Recommendation: revert. A revert PR is already open: Revert "Add a More menu option to switch single-expense reports between expense view and table view" (Expensify/App#103390). Merging it should also clear these blockers that link the same PR:

Expense is not moved to self DM after switching to table view and deleting report from More
Android - Expense - Unable to enter selection mode after switching to table view
Expense- Submit & More button are not disabled during bulk edit after switching to table view
Expense - Submit button on the floating menu is not responsive after switching to table view

How the PR causes it

The PR didn't change the code that breaks. It made that code reachable for "Pay someone" reports for the first time.

The path is new. A "Pay someone" report always has one expense. On production, a one-expense report never shows the table view (prod MoneyRequestReportUtils.ts:172). The PR adds "Switch to table view" for any one-expense report and doesn't exclude "Pay someone" reports (ReportSecondaryActionUtils.ts:1210-1211, MoneyRequestReportUtils.ts:176).
The row press can't find the expense action. The row press (MoneyRequestReportTransactionList.tsx:265) looks up the IOU action that created the expense (useNavigateToTransactionThread.ts:66). In a "Pay someone" report, that action has type pay (SendMoney.ts:153-161). The lookup skips pay actions (ReportActionsUtils.ts:2852-2853, ReportActionsUtils.ts:2878), so it finds nothing.
The app opens an empty thread. With no action found, the hook creates a new expense thread with no link to the expense (useNavigateToTransactionThread.ts:80, Report/index.ts:2494). It then opens that thread in the RHP (useNavigateToTransactionThread.ts:112). This matches the brief "not here" page on Android.
The RHP closes. Likely the server rejects the thread, and the app treats it as deleted and navigates back to the parent report (ReportNavigateAwayHandler.tsx:232-233). This step is inferred from code and not confirmed with a repro.

Ruled out: the one-transaction redirect. The PR disables it in table view (OneTransactionThreadRedirectHandler.tsx:97), and it doesn't fire for "Pay someone" threads (useIsOneTransactionThread.ts:21).

If you roll forward instead: hide "Switch to table view" for "Pay someone" reports, or let the lookup in step 2 accept the pay action for those reports.

Next Steps: Reply with @MelvinBot <your feedback> to refine this analysis.

view run

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.