Skip to content

Show export status in one app-level modal instead of per screen - #98521

Open
mollfpr wants to merge 19 commits into
mainfrom
mollfpr-export-status-manager
Open

Show export status in one app-level modal instead of per screen#98521
mollfpr wants to merge 19 commits into
mainfrom
mollfpr-export-status-manager

Conversation

@mollfpr

@mollfpr mollfpr commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Before, each screen that could start an export (the money report header, Search, and so on) rendered it's own export status modal, and those had to kept in sync.

This moves it to single app-level component, ExportDownloadStatusManager, that watches the exportDownload Onyx collection and owns the one modal. A screen now just starts an export, which writes the record, and ExportDownloadStatusManager handles the rest.

ExportDownloadStatusManager will skips any record with shouldSendFromConcierge and the modal just closes.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/662909
PROPOSAL:

Tests

Same as QA steps.

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Prerequisite:

  • Account with multiple reports
  1. Open the Spend > Reports page
  2. Select multiple reports
  3. Click on the selected reports options
  4. Click on Download as PDF
  5. While the modal is showing "Preparing download...", reload the page
  6. Verify the export modal is resurface
  7. Wait until the export is finished and shows "Your file is ready!", reload the page
  8. Verify the export modal is resurface
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.Aug.16.2026.mp4

@mollfpr

mollfpr commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@mollfpr mollfpr changed the title Mollfpr export status manager Show export status in one app-level modal instead of per screen Aug 13, 2026
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 5de1e8791e

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…-manager

# Conflicts:
#	src/components/MoneyReportHeader.tsx
#	src/components/MoneyReportHeaderActions/ExportDownloadStatusProvider.tsx
#	src/hooks/useExportActions.ts
#	src/hooks/useSearchBulkActions.ts
#	tests/unit/hooks/useExportActionsTest.ts
#	tests/unit/hooks/useSearchBulkActionsTest.ts
@codecov

codecov Bot commented Aug 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/components/ExportDownloadStatusModal.tsx 89.61% <100.00%> (+0.13%) ⬆️
.../MoneyRequestReportView/SelectionToolbar/index.tsx 75.00% <ø> (+0.51%) ⬆️
src/components/Search/SearchBulkActionsButton.tsx 91.35% <ø> (ø)
src/hooks/useExportActions.ts 61.17% <100.00%> (+0.25%) ⬆️
src/libs/Navigation/AppNavigator/AuthScreens.tsx 83.33% <100.00%> (+0.17%) ⬆️
src/components/MoneyReportHeader.tsx 0.00% <0.00%> (ø)
src/hooks/useSearchBulkActions.ts 65.35% <93.75%> (+0.23%) ⬆️
src/libs/actions/Export.ts 78.26% <85.71%> (+0.76%) ⬆️
src/components/ExportDownloadStatusManager.tsx 25.00% <25.00%> (ø)
... and 13 files with indirect coverage changes

@github-actions

Copy link
Copy Markdown
Contributor

🚧 mollfpr has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@mollfpr

mollfpr commented Aug 16, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@github-actions

Copy link
Copy Markdown
Contributor

🚧 mollfpr has triggered a test Expensify/App build. You can view the workflow run here.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5e3b37d85e

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/components/ExportDownloadStatusManager.tsx Outdated
@github-actions

This comment has been minimized.

@mollfpr

mollfpr commented Aug 16, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6e945114cd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/libs/actions/Export.ts
@mollfpr

mollfpr commented Aug 16, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 06a0792cb6

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/components/ExportDownloadStatusManager.tsx
Comment thread src/components/ExportDownloadStatusManager.tsx
@mollfpr

mollfpr commented Aug 16, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Nice work!

Reviewed commit: cb1aed777c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@github-actions

Copy link
Copy Markdown
Contributor

🚧 mollfpr has triggered a test Expensify/App build. You can view the workflow run here.

@mollfpr
mollfpr marked this pull request as ready for review August 16, 2026 14:26
@mollfpr
mollfpr requested review from a team as code owners August 16, 2026 14:26
@melvin-bot
melvin-bot Bot requested review from Ollyws and heyjennahay and removed request for a team and Ollyws August 16, 2026 14:26
@melvin-bot

melvin-bot Bot commented Aug 16, 2026

Copy link
Copy Markdown

@Ollyws Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cb1aed777c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/components/ExportDownloadStatusManager.tsx
Comment thread src/components/ExportDownloadStatusManager.tsx
Comment thread src/libs/actions/Export.ts Outdated
Comment thread src/components/MoneyRequestReportView/SelectionToolbar/index.tsx
Comment thread src/hooks/useExportActions.ts Outdated
Comment thread src/hooks/useSearchBulkActions.ts Outdated
Comment thread src/hooks/useSearchBulkActions.ts Outdated
Comment thread src/hooks/useSearchBulkActions.ts Outdated
@mollfpr
mollfpr requested a review from Ollyws August 17, 2026 07:17
@mollfpr

mollfpr commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@mollfpr

mollfpr commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

@Ollyws are you available to review this PR? Thanks!

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 697be310f9

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +20 to +22
const [exportDownloads] = useOnyx(ONYXKEYS.COLLECTION.EXPORT_DOWNLOAD);

const activeEntry = Object.entries(exportDownloads ?? {}).find(([, exportDownload]) => {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Render export status only in the owning tab

When the same account is open in multiple browser tabs, this shared Onyx collection causes every AuthScreens instance to select the export and render the covering modal, so an export started in one tab still interrupts every other tab and a follower can dismiss or hand off the initiator's export. Fresh evidence is that the new isClientTheLeader() guard only suppresses the automatic fileDownload; it does not prevent this manager from rendering in follower tabs. Scope the manager to the owning/leader client rather than merely gating the download effect.

Useful? React with 👍 / 👎.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant