Skip to content

[Due for payment 2025-06-12] [Due for payment 2025-05-27] Expense - "Review duplicates" button is unresponsive on expenses report. #61973

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.45-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: N/A
Email or phone of affected tester (no customers): ibellicotest+725@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Money Requests

Action Performed:

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Submit two similar expenses.
  4. Open the expenses report.
  5. Tap on "Review Duplicates" on top of the report.
  6. Note that no action is triggered with this action.

Expected Result:

When tapping on "Review Duplicates" on expenses report, the user should be able to begin the process to resolve the duplicates.

Actual Result:

"Review Duplicates" button is unresponsive on expenses report.

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

Bug6830331_1747178525907.Resolve.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @lydiabarclay

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 May 14, 2025
  2. melvin-bot commented on May 14, 2025

    @melvin-bot

    Triggered auto assignment to @lydiabarclay (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 May 14, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 14, 2025

    @melvin-bot

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

  5. github-actions commented on May 14, 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. mollfpr commented on May 14, 2025

    @mollfpr
    Contributor

    This is a regression from #60292

    cc @VickyStash @hungvu193

    Image
  7. removed
    DeployBlockerIndicates it should block deploying the API
    on May 14, 2025
  8. 31 remaining items

  9. melvin-bot commented on May 27, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @hungvu193 owed $250 via NewDot
    • Contributor: @VickyStash is from an agency-contributor and not due payment

    BugZero Checklist (@lydiabarclay)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  10. lydiabarclay commented on May 27, 2025

    @lydiabarclay
    Contributor
    • As per this comment, this is a regression so no payment is due on this GH
    • Just waiting on bz checklist/regression test confirmation, then can create regression test GH if needed, and close
  11. hungvu193 commented on May 28, 2025

    @hungvu193
    Contributor

    The linked PR was reverted and the steps in the OP already catched this bug, so I don't think we need regression test for this one. Feel free to close.

  12. changed the title [-][Due for payment 2025-05-27] Expense - "Review duplicates" button is unresponsive on expenses report.[/-] [+][Due for payment 2025-06-12] [Due for payment 2025-05-27] Expense - "Review duplicates" button is unresponsive on expenses report.[/+] on Jun 5, 2025
  13. melvin-bot commented on Jun 5, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  14. melvin-bot commented on Jun 5, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.59-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-06-12. 🎊

    For reference, here are some details about the assignees on this issue:

    • @hungvu193 requires payment through NewDot Manual Requests
    • @VickyStash does not require payment (Contractor)
  15. melvin-bot commented on Jun 5, 2025

    @melvin-bot

    @hungvu193 @lydiabarclay @hungvu193 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions