Skip to content

Expense - Expense which is not selected still persists after resolving duplicates #67832

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.89-1
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): diojsdjoinjsosi@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit two expenses with the same amount. merchant and category.
  4. Open expense report.
  5. Open expense row.
  6. Click Review duplicates.
  7. Select Keep this one on any expense.
  8. Click Confirm.

Expected Result:

The other expense which is not selected will be deleted.

Actual Result:

The other expense which is not selected still persists after resolving duplicates.

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

Bug6907719_1754341717050.20250805_050601.mp4

View all open jobs on GitHub

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 Aug 5, 2025
  2. github-actions commented on Aug 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.
  3. melvin-bot commented on Aug 5, 2025

    @melvin-bot

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

  4. melvin-bot commented on Aug 5, 2025

    @melvin-bot

    Triggered auto assignment to @stephanieelliott (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.

  5. melvin-bot commented on Aug 5, 2025

    @melvin-bot

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

  6. jasperhuangg commented on Aug 5, 2025

    @jasperhuangg
    Contributor

    @BlameGPT what caused this

  7. BlameGPT commented on Aug 5, 2025

    @BlameGPT
    Contributor

    Needs a vibe check ASAP

    If not above, check these

  8. yuwenmemon commented on Aug 5, 2025

    @yuwenmemon
    Contributor

    Looks like this one has been resolved on the latest staging version: 9.1.89-12

  9. yuwenmemon commented on Aug 5, 2025

    @yuwenmemon
    Contributor
    Kapture.2025-08-05.at.13.28.11.mp4
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.DeployBlockerIndicates it should block deploying the APIEngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions