[$250] Report - The export file does not receive in Concierge chat once online again

[jponikarchuk]

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.3.50-2
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/test-runs/TR-13911/folder/14961849/44241406/1286349403
Email or phone of affected tester (no customers): applausetester+exportemplate@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 11 / Chrome
App Component: Other

Action Performed:

Precondition : Log in with applausetester+exportemplate@applause.expensifail.com

1. Go offline
2. Go to the Reports page > Reports
3. Select two reports on the same workspace
4. Click the x selected green button for more options, then Export
5. Select All Data - report level
6. Go to Concierge chat

Expected Result:

When exporting a report while being offline, the export file is received in Concierge chat once online again

Actual Result:

the export file does not receive in Concierge chat once online again

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @abdulrahuman5196

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022038008198792640851
• Upwork Job ID: 2038008198792640851
• Last Price Increase: 2026-04-18

[MelvinBot]

🚨 Edited by proposal-police: This proposal was edited at 2026-04-25 08:29:03 UTC.

Proposal (Updated 2026-04-25)

What is the root cause of that problem?

When a user exports reports while offline, premature offline guards block the export request from ever being queued via API.write(). Since API.write() persists requests to SequentialQueue and automatically retries when connectivity returns, blocking it is unnecessary and prevents offline export from working.

The offline guards exist in three locations:

1. beginExportWithTemplate in useSearchBulkActions.ts:367-370 — Bulk search export with templates. The guard at line 367 returns early before queueExportSearchWithTemplate() (which uses API.write()) is reached.

2. beginExportWithTemplate in useExportActions.ts:113-116 — Single-report template export (used by MoneyReportHeaderSelectionDropdown). Same issue: the guard blocks queueExportSearchWithTemplate() from being called.

3. handleBasicExport in useSearchBulkActions.ts:431-434 — Basic CSV export. This function has two code paths: queueExportSearchItemsToCSV() (line 454, uses API.write(), works offline) and exportSearchItemsToCSV() (line 466, uses fetch(), cannot work offline). The guard blocks both paths indiscriminately.

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

1. Remove the offline guard from beginExportWithTemplate in useSearchBulkActions.ts (lines 367-370). queueExportSearchWithTemplate uses API.write(), so the request will be automatically persisted and sent on reconnect. Also remove isOffline from the dependency array at line 405.

2. Remove the offline guard from beginExportWithTemplate in useExportActions.ts (lines 113-116). Same reasoning — queueExportSearchWithTemplate uses API.write().

3. In handleBasicExport in useSearchBulkActions.ts: Move the offline guard (lines 431-434) so it only blocks the direct download path (exportSearchItemsToCSV at line 466 which uses fetch() and cannot work offline), but still allows the "all matching items" queued path (queueExportSearchItemsToCSV at line 454 which uses API.write()).

What alternative solutions did you explore? (Optional)

An alternative would be to add optimistic/failure Onyx data to queueExportSearchWithTemplate and queueExportSearchItemsToCSV so the user gets visual feedback if the queued request ultimately fails server-side. Currently these API.write() calls pass no onyxData, so a server-side failure would be silent. This could be a follow-up improvement but is not strictly necessary to fix the offline queuing issue.

---

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.

[melvin-bot]

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

[melvin-bot]

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

[wildan-m]

Proposal

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

When exporting a report while offline (e.g. "All Data - report level"), the export request is silently discarded. The export file is never received in Concierge chat even after going back online.

What is the root cause of that problem?

The export functions use API.write() via queueExportSearchWithTemplate() / queueExportSearchItemsToCSV(), which is the offline-first API method that automatically persists requests to SequentialQueue and retries them when the device reconnects. However, there are premature offline guards that return early before these API.write() calls are ever reached, so the request is never queued.

1. Template export — bulk search path (beginExportWithTemplate in useSearchBulkActions.ts):

App/src/hooks/useSearchBulkActions.ts

Lines 242 to 245 in ef87510

	if (isOffline) {
	setIsOfflineModalVisible(true);
	return;
	}

This guard shows the offline modal and returns before queueExportSearchWithTemplate() at line 248 is reached. Since queueExportSearchWithTemplate calls API.write():

App/src/libs/actions/Search.ts

Lines 1301 to 1312 in ef87510

	const finalParameters = enhanceParameters(WRITE_COMMANDS.QUEUE_EXPORT_SEARCH_WITH_TEMPLATE, {
	templateName,
	templateType,
	jsonQuery,
	reportIDList,
	transactionIDList,
	policyID,
	}) as ExportSearchWithTemplateParams;
	API.write(WRITE_COMMANDS.QUEUE_EXPORT_SEARCH_WITH_TEMPLATE, finalParameters);
	}

...the request would be automatically persisted and sent on reconnect if the guard weren't blocking it.

2. Template export — single report path (beginExportWithTemplate in MoneyReportHeader.tsx):

App/src/components/MoneyReportHeader.tsx

Lines 580 to 582 in ef87510

	if (isOffline) {
	setOfflineModalVisible(true);
	return;

Same pattern — the offline guard blocks queueExportSearchWithTemplate() at line 595.

3. Basic CSV export (handleBasicExport in useSearchBulkActions.ts):

App/src/hooks/useSearchBulkActions.ts

Lines 306 to 309 in ef87510

	if (isOffline) {
	setIsOfflineModalVisible(true);
	return;
	}

This top-level guard blocks both the queued path (queueExportSearchItemsToCSV at line 329, which uses API.write()) and the direct download path (exportSearchItemsToCSV at line 341, which uses fileDownload()/fetch()). The queued path should be allowed offline; only the direct download path genuinely requires connectivity.

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

1. Remove the offline guard from beginExportWithTemplate in useSearchBulkActions.ts (lines 242-245). The existing confirmation modal ("Concierge will send you the file shortly") already sets the correct user expectation for both online and offline scenarios.

2. Remove the offline guard from beginExportWithTemplate in MoneyReportHeader.tsx (lines 580-582).

3. In handleBasicExport (useSearchBulkActions.ts): remove the top-level offline guard (lines 306-309) and add it only before the direct download branch (before line 340) — this unblocks the areAllMatchingItemsSelected queued path while keeping the offline guard on the exportSearchItemsToCSV path that genuinely requires fetch().

Compare branch: https://github.com/Expensify/App/compare/main...wildan-m:App:wildan/86614-export-offline-fix?expand=1

What alternative solutions did you explore? (Optional)

For handleBasicExport, instead of keeping the offline modal for the direct download path, we could fall back to queueExportSearchItemsToCSV when offline — so the user always gets the export via Concierge. However, this would change the delivery method from a direct browser download to a Concierge message, which may confuse users who initiated a direct CSV export. Keeping the offline modal for the direct download path is more conservative and preserves the expected UX.

[wildan-m]

Proposal

Updated

Added compare branch with implementation.

[Ltbltbltbltb]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[melvin-bot]

📣 @Ltbltbltbltb! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>