[Due for payment 2026-03-30] Expense - Expense auto enters selection mode after clicking Move to report

[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.39-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: #85038
Email or phone of affected tester (no customers): sjdoisjoisdjonsnjo@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:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create two expenses.
4. Open expense report.
5. Open any expense.
6. Click More > Move to report.
7. Close the RHP.
8. Close expense details RHP.

Expected Result:

Expense will not enter selection mode.

Actual Result:

Expense auto enters selection mode after clicking Move to report, even after RHP is closed.

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

[melvin-bot]

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

[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: #85038 - "Feat: Add 'Move to report' in the 'More' menu of a one-expense report" by @nyomanjyotisa (High confidence)
Related Issues: None

Recommendation: REVERT

PR #85038 introduced a "Move to report" option in the More menu for single-expense reports. When this action is triggered, it calls setSelectedTransactions([transactionID]) to mark the transaction for moving. However, the selected transaction state persists in SearchContext even after the RHP is closed. The useHandleSelectionMode hook then detects this populated selectedTransactionIDs array and automatically activates mobile selection mode, causing the expense to unexpectedly enter selection mode.

This is the exact behavior reported in the issue: "Expense auto enters selection mode after clicking Move to report, even after RHP is closed."

Labels: Keeping DeployBlockerCash (frontend bug blocking App deploy)

Detailed Analysis

Evidence

• The bug is reproducible only on staging where PR Feat: Add 'Move to report' in the 'More' menu of a one-expense report #85038 is deployed
• The bug does not exist in production (as noted: "N/A - new feature, doesn't exist in prod")
• The reproduction steps exactly match the new "Move to report" feature added in PR Feat: Add 'Move to report' in the 'More' menu of a one-expense report #85038
• melvin-bot automatically assigned the issue to the PR Feat: Add 'Move to report' in the 'More' menu of a one-expense report #85038 author

Verification

PR #85038 modified the following files related to the bug:

• src/components/MoneyReportHeader.tsx - Added Move Expense secondary action (line 1120-1137 in diff)
• src/components/MoneyRequestHeader.tsx - Added Move Expense secondary action (line 211-236 in diff)
• src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx - Uses useHandleSelectionMode hook
• src/hooks/useHandleSelectionMode.ts - Automatically turns on selection mode when selectedTransactionIDs.length > 0

Root Cause

When the user clicks "Move to report" from the More menu:

1. MoneyReportHeader.tsx (line 134 in diff):

setSelectedTransactions([transactionToMove.transactionID]);
Navigation.navigate(ROUTES.MONEY_REQUEST_EDIT_REPORT.getRoute(...));

2. MoneyRequestHeader.tsx (line 232 in diff):

setSelectedTransactions([transaction.transactionID]);
Navigation.navigate(ROUTES.MONEY_REQUEST_EDIT_REPORT.getRoute(...));

These calls populate the selectedTransactionIDs in SearchContext, which persists even after navigation or RHP closure.

3. MoneyRequestReportTransactionList.tsx (line 225):

const {selectedTransactionIDs} = useSearchStateContext();
useHandleSelectionMode(selectedTransactionIDs);

4. useHandleSelectionMode.ts (lines 30-31):

if (selectedItems.length > 0 && !isMobileSelectionModeEnabled) {
    turnOnMobileSelectionMode();
}

When the user returns to the expense report view after closing the RHP, useHandleSelectionMode detects the persisted selected transaction and automatically activates mobile selection mode, causing the unexpected behavior.

The fix should either:

• Clear selected transactions when the "Move to report" flow completes or is cancelled
• Use a different mechanism for tracking which transaction to move that doesn't trigger selection mode
• Prevent useHandleSelectionMode from activating when transactions are selected for non-selection-mode purposes