Expense - Expense RHP opens after selecting expense during review duplicates flow

[applause-bot]

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.79-1
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: #89587
Email or phone of affected tester (no customers): sdsdjoijdoisnjodis@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 with same amount.
4. Open the report.
5. Click Review duplicates.
6. Select other expense.

Expected Result:

The expense will be marked as selected without opening expense RHP.

Actual Result:

Expense RHP opens after selecting expense.
User cannot click Keep selected after selecting another expense.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7160100_1779400670220.3.mp4

View all open jobs on GitHub

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

[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/bba3fd61b0cfed87efdf3124f0654cdd0fa792c61925d62a308445af01edc98c

[melvin-bot]

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

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

Proposal

What is the root cause of that problem?

PR #89587 replaced the old ReportActionItem-based rendering in the duplicate review screen with a PressableWithFeedback wrapper around TransactionItemRow. This outer pressable has onPress={handlePreviewPress}, which navigates to the expense RHP via ROUTES.SEARCH_REPORT.

When the user taps the radio button to select a different transaction, the radio button's onPress correctly fires and calls onSelectTransaction (line 97), but the press event bubbles up to the outer PressableWithFeedback, which also fires handlePreviewPress and opens the expense RHP. The RadioButton component does not stop propagation of the press/click event.

What changes do you think we should make in order to solve the problem?

In DuplicateTransactionItem.tsx, the onRadioButtonPress callback should be updated to stop event propagation so it doesn't bubble up to the outer PressableWithFeedback. The callback should accept the event and call e.stopPropagation() before calling onSelectTransaction.

Alternatively, the shouldStopPropagation prop could be passed to the RadioButton / SelectionButton component if supported, to prevent the press from reaching the parent pressable.

What alternative solutions did you explore? (Optional)

Another option would be to change the outer PressableWithFeedback's onPress from handlePreviewPress to onSelectTransaction (making tapping anywhere on the row select the transaction), and provide a separate smaller pressable target for navigation. However, this would be a larger behavioral change and the event propagation fix is more targeted and lower-risk for a deploy blocker.

Investigation details

Event flow:

1. User taps radio button area in DuplicateTransactionItem
2. RadioButton.onPress fires → calls onRadioButtonPress → calls setSelectedTransactionID ✅
3. Press event bubbles up through TransactionItemRowNarrow → View hierarchy
4. Outer PressableWithFeedback at line 72 catches the bubbled event
5. handlePreviewPress fires → navigates to expense RHP ❌

Key files:

• DuplicateTransactionItem.tsx:72-79 — outer pressable with navigation handler
• DuplicateTransactionItem.tsx:97 — radio button press handler (missing stopPropagation)
• TransactionItemRowNarrow.tsx:155-165 — radio button rendering
• Review.tsx:154-163 — onPreviewPressed navigates to RHP

Regression source: #89587 (merged 2026-05-21)

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[deetergp]

@MelvinBot Can you determine which PR caused this?