[$250] Duplicate expenses - Expense appears twice after keeping one of the duplicates

[mitarachim]

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.1.59-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): sdonjoisjoooj@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit two same expenses with category.
4. Click on the expense preview.
5. Open each of the expenses then close it.
6. Go offline.
7. Click Review duplicates on the expense report.
8. Click Keep this one on any expense.
9. Click Confirm on the confirmation page.

Expected Result:

The transaction will not appear twice after keeping one of the duplicates.

Actual Result:

The transaction appears twice after keeping one of the duplicates - first is the transaction details, second is the expense preview under the transaction details.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6851087_1749082346676.20250605_080745.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021930539598495024271
• Upwork Job ID: 1930539598495024271
• Last Price Increase: 2025-06-05

Issue Owner

Current Issue Owner: @suneox

[melvin-bot]

Triggered auto assignment to @dylanexpensify (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 @robertjchen (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[BlameGPT]

Possible culprit PRs for this issue

• Stop creating the transaction thread reports optimistically for RequestMoney #62080: This PR involves transaction thread reports and duplicate expense flows, including 'Review duplicates' button behavior matching the issue reproduction steps.
• Preview shows Deleted report when new report is created offline when workflows are disabled #63142: This PR deals with expense preview behavior offline and report creation, which aligns with steps involving expense preview and offline mode in the issue.
• Fix - receipt empty state border regression #62832: This PR includes test steps for submitting duplicate expenses, reviewing duplicates, and confirming on the confirmation page, directly matching the issue reproduction steps.