You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-06-25] [$250] Spend - Expense-level export fails with “You can't export empty report” #91930
Version Number: V9.3.84-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:#84382 Email or phone of affected tester (no customers):dreamnitethedragon+vegst@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Redmi note 10s android 13 App Component: Money Requests
Action Performed:
Launch app
Go to self DM
Create a manual expense
Open the expense and split the expense by date ( selecting few dates)
Go to spend
Select all the expense - Export - All data Expense level
Expected Result:
When selecting all data expense level download failed must not be shown.
Actual Result:
When selecting all data expense level- download failed - you can't export empty report is shown.
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Spend-Expense-level export fails with “You can't export empty report”[/-][+]Spend - Expense-level export fails with “You can't export empty report”[/+]on May 28, 2026
When the user selects these transactions on the Spend page and exports, selectedTransactionReportIDs collects '0' as a report ID (no filter excludes it). The client-side empty-report guard at line 459-473 only checks selectedReports, which is always empty on the expense-level view. So '0' is sent to the backend as a report ID, the backend can't find a real report, and returns the "empty report" error.
What changes do you think we should make in order to solve the problem?
Filter out UNREPORTED_REPORT_ID ('0') from selectedTransactionReportIDs in useSearchBulkActions.ts:349. Change the filter from:
.filter((reportID) => reportID !== undefined)
to also exclude CONST.REPORT.UNREPORTED_REPORT_ID:
This prevents the invalid report ID from reaching both beginExportWithTemplate and handleBasicExport, which both use selectedTransactionReportIDs as the reportIDList. The transaction IDs are still sent separately, so the backend can still export the actual transaction data.
What alternative solutions did you explore? (Optional)
An alternative would be to add guards inside beginExportWithTemplate and handleBasicExport individually, but filtering at the source (selectedTransactionReportIDs) is cleaner since it fixes all downstream consumers at once.
Another option would be to assign child split transactions a real self-DM report ID instead of '0', but UNREPORTED_REPORT_ID is an intentional design choice for self-DM splits that other flows depend on, so changing it would have broader implications.
Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.
Activity
applause-bot commentedon May 28, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/426d15deca739ad5939f7bf0457b7772a4294d119b6bf6a682c32c9662e417c4
melvin-bot commentedon May 28, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #84382
melvin-bot commentedon May 28, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 28, 2026
👋 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:
[-]Spend-Expense-level export fails with “You can't export empty report”[/-][+]Spend - Expense-level export fails with “You can't export empty report”[/+]MelvinBot commentedon May 28, 2026
Proposal
What is the root cause of that problem?
When a self-DM expense is split by date (feature added in #84382), child transactions are assigned
reportID: '0'(UNREPORTED_REPORT_ID) atMoneyRequestBuilder.ts:1388andSplitTransactionUpdate.ts:639-644.When the user selects these transactions on the Spend page and exports,
selectedTransactionReportIDscollects'0'as a report ID (no filter excludes it). The client-side empty-report guard at line 459-473 only checksselectedReports, which is always empty on the expense-level view. So'0'is sent to the backend as a report ID, the backend can't find a real report, and returns the "empty report" error.What changes do you think we should make in order to solve the problem?
Filter out
UNREPORTED_REPORT_ID('0') fromselectedTransactionReportIDsinuseSearchBulkActions.ts:349. Change the filter from:to also exclude
CONST.REPORT.UNREPORTED_REPORT_ID:This prevents the invalid report ID from reaching both
beginExportWithTemplateandhandleBasicExport, which both useselectedTransactionReportIDsas thereportIDList. The transaction IDs are still sent separately, so the backend can still export the actual transaction data.What alternative solutions did you explore? (Optional)
An alternative would be to add guards inside
beginExportWithTemplateandhandleBasicExportindividually, but filtering at the source (selectedTransactionReportIDs) is cleaner since it fixes all downstream consumers at once.Another option would be to assign child split transactions a real self-DM report ID instead of
'0', butUNREPORTED_REPORT_IDis an intentional design choice for self-DM splits that other flows depend on, so changing it would have broader implications.Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.emkhalid commentedon May 28, 2026
ZhenjaHorbach commentedon May 28, 2026
@emkhalid
It's not open for proposals
81 remaining items
melvin-bot commentedon Jun 24, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Jun 24, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Jun 27, 2026
Payment Summary
Contributor: @KJ21-ENG paid $250 via Upwork
Contributor+: @gijoe0295 due $250 via NewDot
@KJ21-ENG can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022060342029287398175
^ Test case created. Thx
KJ21-ENG commentedon Jun 27, 2026
@mallenexpensify Accepted. Thanks!
mallenexpensify commentedon Jun 27, 2026
@KJ21-ENG paid, summary updated above. Thx.
JmillsExpensify commentedon Jun 29, 2026
$250 approved for @gijoe0295