Skip to content

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

Closed

Description

@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 OwnerCurrent Issue Owner: @suneox

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jun 5, 2025
  2. melvin-bot commented on Jun 5, 2025

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

  3. melvin-bot commented on Jun 5, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jun 5, 2025

    @melvin-bot

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

  5. github-actions commented on Jun 5, 2025

    @github-actions
    Contributor

    👋 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.
  6. BlameGPT commented on Jun 5, 2025

    @BlameGPT
    Contributor

    Possible culprit PRs for this issue

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jun 5, 2025
  8. changed the title [-]Duplicate expenses - Expense appears twice after keeping one of the duplicates[/-] [+][$250] Duplicate expenses - Expense appears twice after keeping one of the duplicates[/+] on Jun 5, 2025
  9. melvin-bot commented on Jun 5, 2025

    @melvin-bot
  10. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 5, 2025
  11. melvin-bot commented on Jun 5, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox (External)

  12. VickyStash commented on Jun 5, 2025

    @VickyStash
    Contributor

    This issue was caused by this PR: #62080 it was reverted here: #63542

  13. robertjchen commented on Jun 10, 2025

    @robertjchen
    Contributor

    thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions