Report - Both expenses disappear after keeping one duplicate.

[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.15.1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-4455/folder/13176704/41236827/1172745669
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - 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. Open any workspace chat.
3. Create two similar manual expenses.
4. Open the report of the just created expenses.
5. Open the first expense.
6. Tap on "Review Duplicates"
7. Tap on "Keep this one" on the second expense.
8. Note that you are redirected to a "It´s not here" page.
9. Return to chat.
10. Note that both expenses disappeared.

Expected Result:

After keeping one duplicate expense, user shoud land on report again and information of the kept expense should be visible.

Actual Result:

After keeping one duplicate expense, user lands on a "It´s not here" page and both expenses disappear.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

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

[melvin-bot]

Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @marcaaron (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #80726 - "Perf: Split WideRHPContext into State and Actions" by @staszekscp (High confidence)
Related Issues: This is a regression of #73058, which was previously fixed by #76020

Recommendation: REVERT

PR #80726 introduced a regression that removed the fix from PR #76020. The closeReviewDuplicates function that properly navigates back to the report before dismissing the modal was removed during the refactoring.

Labels: Keep DeployBlockerCash (App deploy is blocked). This PR is in the App repository and needs to be reverted/fixed there.

Detailed Analysis

Evidence

1. The bug symptoms match exactly: After keeping one duplicate expense, users land on "Its not here" page and both expenses disappear
2. Previous fix was lost: PR Fix duplicate-review confirmation redirecting to “It’s not here” #76020 fixed this exact issue on December 5, 2025 by adding a closeReviewDuplicates function that:
   • Navigates to SEARCH_MONEY_REQUEST_REPORT with the report ID before dismissing
   • Ensures the user lands on the correct report after resolving duplicates
3. PR Perf: Split WideRHPContext into State and Actions #80726 removed the fix: When refactoring WideRHPContext on January 28, 2026, the closeReviewDuplicates function was lost, likely during merge conflict resolution or incomplete porting of changes

Verification

Current broken code (lines 92-95 in src/pages/TransactionDuplicate/Confirmation.tsx):

const handleResolveDuplicates = useCallback(() => {
    resolveDuplicates(transactionsMergeParams);
    Navigation.dismissToSuperWideRHP();
}, [transactionsMergeParams]);

What was working (from PR #76020):

const closeReviewDuplicates = useCallback(() => {
    if (reviewDuplicates?.reportID) {
        Navigation.setNavigationActionToMicrotaskQueue(() => {
            Navigation.navigate(ROUTES.SEARCH_MONEY_REQUEST_REPORT.getRoute({reportID: reviewDuplicates.reportID}), {forceReplace: true});
        });
    }
    Navigation.dismissModal();
}, [reviewDuplicates?.reportID]);

const handleResolveDuplicates = useCallback(() => {
    closeReviewDuplicates();
    IOU.resolveDuplicates(transactionsMergeParams);
}, [transactionsMergeParams, closeReviewDuplicates]);

Why it breaks:

• Navigation.dismissToSuperWideRHP() is called unconditionally without checking if super wide RHP is actually displayed
• No navigation back to the source report occurs before dismissing, causing the "Its not here" page
• The resolveDuplicates action removes the duplicate expense violations, making both expenses appear to "disappear" when navigation fails

Root Cause

PR #80726 changed context usage from useContext(WideRHPContext) to useWideRHPState() but during the refactoring or merge, the closeReviewDuplicates function and its usage were not properly preserved. The handleResolveDuplicates function reverted to an earlier, broken implementation that only calls Navigation.dismissToSuperWideRHP().

Additionally, handleResolveDuplicates should check isSuperWideRHPDisplayed similar to how handleMergeDuplicates does (lines 85-90), but this logic is missing.

[marcaaron]

The PR referenced above is on production now. Though, does seem like it could be related to that general area of the codebase.

[marcaaron]

This is the offending PR: #81079