Skip to content

[Due for payment 2026-06-09] [Due for payment 2026-06-09] Spend - Unable to export current view on Spend > Awaiting export #92257

Closed

Description

@applause-bot

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.90-1
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: #90714
Email or phone of affected tester (no customers): sjndojsodjosdjojs@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Search

Action Performed:

Precondition:

  • Connect workspace to Sage Intacct.
  • Disable auto-sync on Accounting > Advanced.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Open the report.
  5. Click Submit, Approve and Mark as paid.
  6. Click More > Export > Mark as exported.
  7. Cancel payment and unapprove the same report.
  8. Click Approve and Mark as paid.
  9. Go to Spend > Awaiting export.
  10. Select the report via checkbox.
  11. Click dropdown menu.
  12. Click Export > Export current view.

Expected Result:

Report will be exported.

Actual Result:

Error shows up.

Download failed
Your download couldn't be completed. Please try again later.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7168587_1780320710490.6.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7168587

Activity

  1. applause-bot commented on Jun 1, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/77a4e71f4c1806e9d3be635c75f7b1a6919235794b955c7aa5b381f3e94500df

  2. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 1, 2026
  3. melvin-bot commented on Jun 1, 2026

    @melvin-bot

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

  4. melvin-bot commented on Jun 1, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Jun 1, 2026

    @github-actions
    Contributor

    👋 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.
  6. melvin-bot commented on Jun 1, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  7. MelvinBot commented on Jun 1, 2026

    @MelvinBot
    Contributor

    Issue Analysis

    Root Cause: The new "Export current view" button from #90714 sends isBasicExport: false together with report‑level columns embedded in the jsonQuery for the "Awaiting export" view. App only forwards these params — the CSV is generated server‑side — and the server responds with a JSON error instead of a .csv, which App surfaces as the "Download failed" modal.

    The "Awaiting export" tab (the EXPORT search key) uses search type EXPENSE_REPORT, so getColumnsToShow returns report/UI‑level columns — AVATAR, DATE, STATUS, TITLE, FROM, TO, TOTAL, ACTION. With isBasicExport: false ("current view"), the server is asked to build a CSV from those columns and fails. "Basic export" goes through the same code path but with isBasicExport: true, which is why it still works.

    Confidence: Medium. The App‑side request flow is traced with high confidence; the exact server‑side failure could not be confirmed (log access was unavailable in this run, and the CSV generation lives outside this repo).

    Recommended action (deploy blocker):

    • To unblock the deploy now: revert [Payment due @thesahindia] Add export current view #90714 — the feature is new and not in production, so reverting cleanly removes the failing path.
    • Proper fix: the actual CSV generation and the handling of isBasicExport / exportColumnLabels happen server‑side (outside the App repo), so the root‑cause fix requires a backend change. This needs an internal engineer with backend access to confirm whether the server should support report‑level columns for this export, or whether App should avoid offering "Export current view" / sending report‑level columns for the EXPORT view.
    Investigation details & evidence

    What App sends. Both export buttons now run the same helper: handleBasicExport = handleCSVExport(true) and handleExportCurrentView = handleCSVExport(false) (useSearchBulkActions.ts:710-711). getCSVExportParameters serializes the visible columns into the query via serializeQueryJSONForBackend({...queryJSON, columns: columnsToExport}) and builds an exportColumnLabels map (useSearchBulkActions.ts:598-623). The only difference between the two buttons is the isBasicExport flag.

    Why "Awaiting export" is special. The EXPORT suggested search is typed EXPENSE_REPORT (SearchUIUtils.ts:813-823), so its columns are report‑level (AVATAR/STATUS/TITLE/ACTION, etc.) rather than expense‑row columns.

    Where the error surfaces. App POSTs the params and calls fileDownload(...) (Search.ts:1145-1194). When the server returns application/json (an error) for a .csv request, the download utility throws and invokes onDownloadFailed, which shows the "Download failed" modal. No CSV‑building, isBasicExport, or exportColumnLabels logic exists in the App repo — those are only forwarded as params.

    Alternative considered & ruled out: a missing translation key for an export column would not cause "Download failed" — getSearchColumnTranslationKey has a default fallback (SearchUIUtils.ts:4275-4278) and every column in this view has an explicit case, so translate() never throws here.

    To confirm server‑side: check the ExportSearchToCSV / QueueExportSearchToCSV command logs around 2026-05-31–2026-06-01 for the rejection reason (e.g. unrecognized report‑level columns when isBasicExport=false).


    Next Steps for Contributor+ team:
    To unblock: revert #90714.
    For the real fix: escalate the server-side ExportSearchToCSV behavior to an internal engineer with backend access (root‑cause is outside the App repo).
    To refine: @MelvinBot <your feedback>

  8. inimaga commented on Jun 1, 2026

    @inimaga
    Contributor

    Offending PR now reverted and CP'd. Retest requested.

  9. IuliiaHerets commented on Jun 1, 2026

    @IuliiaHerets

    Chrome / 9.3.90-3
    No Export current view option

    REC-20260601220605.mp4
  10. added and removed
    ReviewingHas a PR in review
    on Jun 2, 2026
  11. changed the title [-]Spend - Unable to export current view on Spend > Awaiting export[/-] [+][Due for payment 2026-06-09] Spend - Unable to export current view on Spend > Awaiting export[/+] on Jun 2, 2026
  12. melvin-bot commented on Jun 2, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  13. melvin-bot commented on Jun 2, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.90-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-06-09. 🎊

  14. melvin-bot commented on Jun 2, 2026

    @melvin-bot

    @inimaga The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  15. melvin-bot commented on Jun 2, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.94-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-06-09. 🎊

  16. changed the title [-][Due for payment 2026-06-09] Spend - Unable to export current view on Spend > Awaiting export[/-] [+][Due for payment 2026-06-09] [Due for payment 2026-06-09] Spend - Unable to export current view on Spend > Awaiting export[/+] on Jun 2, 2026
  17. melvin-bot commented on Jun 2, 2026

    @melvin-bot

    @inimaga The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  18. inimaga commented on Jun 3, 2026

    @inimaga
    Contributor

    No checklist needed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions