[Due for payment 2026-01-28] [$250] Expense-Rejected expense preview total resets to 0 after rejection & update only after revisit

[nlemma]

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: V9.2.88-5
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/27754595/test-cases/69505292?q=Reject+
Email or phone of affected tester (no customers): dreamnitethedragon+yydyd373@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redminote 10S Android 13
App Component: Money Requests

Action Performed:

1. Launch app
2. Open workspace chat
3. Create 3 manual expense
4. Open the expense report
5. Tap submit
6. Select 2 expenses and Reject option from dropdown
7. Enter reason and complete the flow
8. Navigate to rejected expense
9. Note Expense preview shows correct total briefly and changes to zero
10. Tap Total
11. Navigate back to expense preview
12. Note correct total is shown now

Expected Result:

Rejected expense preview should consistently display the correct total.

The total should not change unexpectedly or require navigating away and back to display correct total amount.

Actual Result:

Rejected expense preview briefly displays the correct total.

The total then automatically changes to 0 without any user action.

Tapping Total and navigating back to the expense preview updates the total to the correct value.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7039126_1767085416715.Screenrecorder-2025-12-30-14-25-16-826.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022008463768715252552
• Upwork Job ID: 2008463768715252552
• Last Price Increase: 2026-01-06

Issue Owner

Current Issue Owner: @sonialiap

[melvin-bot]

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

[bernhardoj]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Rejected expense report shows 0 amount on the report preview.

What is the root cause of that problem?

When we reject expenses, we create a new report if we don't have one yet. The problem is, on success we use a SET that clears the report.

App/src/libs/actions/IOU/index.ts

Lines 13618 to 13632 in 1d1ea3d

	successData.push(
	{
	onyxMethod: Onyx.METHOD.SET,
	key: `${ONYXKEYS.COLLECTION.REPORT}${rejectedToReportID}`,
	value: {
	pendingFields: null,
	},
	},
	{
	onyxMethod: Onyx.METHOD.SET,
	key: `${ONYXKEYS.COLLECTION.REPORT_METADATA}${rejectedToReportID}`,
	value: {
	isOptimisticReport: null,
	},
	},

So, the amount shown is 0.

There are other bugs too, like report preview action is created for each rejected transaction and the report total will take the last transaction amount, but it's out of scope of this issue.

What changes do you think we should make in order to solve the problem?

We need to use MERGE instead of SET.

App/src/libs/actions/IOU/index.ts

Lines 13618 to 13632 in 1d1ea3d

	successData.push(
	{
	onyxMethod: Onyx.METHOD.SET,
	key: `${ONYXKEYS.COLLECTION.REPORT}${rejectedToReportID}`,
	value: {
	pendingFields: null,
	},
	},
	{
	onyxMethod: Onyx.METHOD.SET,
	key: `${ONYXKEYS.COLLECTION.REPORT_METADATA}${rejectedToReportID}`,
	value: {
	isOptimisticReport: null,
	},
	},

[melvin-bot]

@sonialiap Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022008463768715252552

[melvin-bot]

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

[suneox]

@bernhardoj Thanks for your proposal, but can you still reproduce this on the latest main? On the latest main, after rejecting, I only see an issue with duplicated report groups.

v9.2.96-1

CleanShot.2026-01-09.at.00.30.10.mp4

v9.2.94-0

CleanShot.2026-01-09.at.00.23.51.mp4