Report - Total amount is not correctly updated after bulk duplicating expenses offline.

[lanitochka17]

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.3.58-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #84657
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

1. Open the staging.new.expensify.com website.
2. Open any workspace chat.
3. Turn off internet connection.
4. Create two manual expenses.
5. Open the report of the just created expenses.
6. Select both expenses.
7. Click on dropdown menu > "Duplicate Expenses"
8. Note that after expenses are duplicated, total amount is not correctly updated. Only the amount of one of the duplicates is added to total amount.
9. Turn on internet connection.
10. Note that total amount is now correctly updated.

Expected Result:

After bulk duplicating expenses while offline, total amount should be updated automatically.

Actual Result:

After bulk duplicating expenses while in offline mode, total amount is not updated correclty. Only the amount of one of the duplicates is added to total amount.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7126764_1775826924261.Du_13.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #84657

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

[OSBotify]

Investigation Summary: Classification: Frontend bug. Causing PR: #84657 ("[Duplicate Expense] Allow bulk duplication." by @Krishna2323) - High confidence. Recommendation: REVERT. PR #84657 introduced the bulk duplicate expenses feature with a bug in its offline optimistic update logic. In bulkDuplicateExpenses (src/libs/actions/IOU/Duplicate.ts lines 995-1031), the return value of duplicateExpenseTransaction is never captured, so the updated iouReport total from each iteration is never fed into subsequent iterations. This means only one expense amount is reflected in the optimistic report total until the network reconnects and the server corrects it. By contrast, duplicateReport correctly captures result.iouReport per iteration. The bug is confined to the App codebase, so DeployBlockerCash is kept. Assigned: @Krishna2323 (author), @JS00001 (approving reviewer), @situchan (approving reviewer).