[Due for payment 2025-04-28] Review duplicates - Confirm button is not functional after moving report on confirmation page

[IuliiaHerets]

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.28-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
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): sdjmsdojioisjdos@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Create a workspace.
3. Enable Delayed submissions in Workflows if it is not enabled by default.
4. Go to workspace chat.
5. Submit an expense.
6. Click Submit button on the expense preview.
7. Submit another expense with the same amount and merchant as Step 5.
8. Go to expense report of the expense from Step 7.
9. Click Review duplicates.
10. Click Keep this one on the first expense.
11. Click Report.
12. Select the other report.
13. Click Confirm button.

Expected Result:

In Step 11, Report field should be disabled because we cannot edit other expense details on the confirmation page when reviewing duplicates.

Actual Result:

In Step 11, Report field is not disabled on the confirmation page when reviewing duplicates.
In Step 13, after moving report on the confirmation page, Confirm button is no longer functional.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6802468_1744702735693.20250415_153421.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @laurenreidexpensify

[melvin-bot]

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

[rayane-d]

Discussing in https://expensify.slack.com/archives/C01GTK53T8Q/p1744712146580769

[NikkiWines]

Likely tied to #58597, as this functionality has just been added. Not sure if we want to allow moving transactions to a new report when reviewing duplicates 🤔

What do you think @laurenreidexpensify?

[NikkiWines]

cc: @sumo-slonik @rayane-d @DylanDylann @luacmartins as you reviewed the PR