Skip to content

feat: Enable multi-select Download as PDF#92275

Merged
mollfpr merged 24 commits into
Expensify:mainfrom
truph01:feat/90300
Jun 19, 2026
Merged

feat: Enable multi-select Download as PDF#92275
mollfpr merged 24 commits into
Expensify:mainfrom
truph01:feat/90300

Conversation

@truph01

@truph01 truph01 commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #90300
PROPOSAL:

Tests

  1. Open app
  2. Go to Spend > Reports
  3. Choose more than one report > Click on "X selected" dropdown button > Click on "Download as PDF" option
  4. Verify the below modal is shown:
Screenshot 2026-06-16 at 16 34 13
  1. Wait a minute until the below modal is shown:
Screenshot 2026-06-16 at 16 34 42
  1. Click on "Download file" button.

  2. Verify the pdf files are downloaded.

  3. Do step 1 - 4

  4. Click on “Send me the file when it’s ready”

  5. Wait a few minute and click Go to Concierge

  6. Verify the pdf files is send by Concierge

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Open app
  2. Go to Spend > Reports
  3. Choose more than one report > Click on "X selected" dropdown button > Click on "Download as PDF" option
  4. Verify the below modal is shown:
Screenshot 2026-06-16 at 16 34 13
  1. Wait a minute until the below modal is shown:
Screenshot 2026-06-16 at 16 34 42
  1. Click on "Download file" button.

  2. Verify the pdf files are downloaded.

  3. Do step 1 - 4

  4. Click on “Send me the file when it’s ready”

  5. Wait a few minute and click Go to Concierge

  6. Verify the pdf files is send by Concierge

  • 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 any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • 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)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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
Screen.Recording.2026-06-17.at.14.15.58.mov
iOS: Native
iOS: mWeb Safari
Screen.Recording.2026-06-17.at.14.13.47.mov
MacOS: Chrome / Safari
Screen.Recording.2026-06-17.at.14.08.25.mov

@melvin-bot

melvin-bot Bot commented Jun 1, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@mollfpr

mollfpr commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

@truph01 do you think we need to replace the downloadURL with filename like we did for the CSV export?

@truph01

truph01 commented Jun 9, 2026

Copy link
Copy Markdown
Contributor Author

@truph01 do you think we need to replace the downloadURL with filename like we did for the CSV export?

@mollfpr Yes, i think so

@codecov

codecov Bot commented Jun 15, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/CONST/index.ts 93.84% <ø> (ø)
src/components/ExportDownloadStatusModal.tsx 96.66% <100.00%> (+0.37%) ⬆️
src/components/Search/SearchBulkActionsButton.tsx 1.58% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
src/libs/UrlUtils.ts 100.00% <100.00%> (ø)
src/libs/actions/Export.ts 100.00% <100.00%> (ø)
src/libs/actions/Search.ts 38.61% <ø> (ø)
src/hooks/useSearchBulkActions.ts 55.54% <90.00%> (+0.20%) ⬆️
src/libs/TravelInvoicingUtils.ts 82.97% <0.00%> (ø)
src/pages/wallet/WalletStatementPage.tsx 0.00% <0.00%> (ø)
... and 1 more
... and 11 files with indirect coverage changes

@truph01 truph01 marked this pull request as ready for review June 15, 2026 04:11
@truph01 truph01 requested review from a team as code owners June 15, 2026 04:11
@melvin-bot melvin-bot Bot requested review from daledah and trjExpensify and removed request for a team June 15, 2026 04:11
@melvin-bot

melvin-bot Bot commented Jun 15, 2026

Copy link
Copy Markdown

@daledah 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]

@truph01

truph01 commented Jun 15, 2026

Copy link
Copy Markdown
Contributor Author

@daledah We're currently waiting for the backend PR that handles this:

@truph01 do you think we need to replace the downloadURL with filename like we did for the CSV export?

to be deployed. In the meantime, feel free to review the changes.

@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: 43857b14fe

ℹ️ 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 +90 to +95
const failureData: AnyOnyxUpdate[] = [
{
onyxMethod: Onyx.METHOD.SET,
key: onyxKey,
value: null,
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep failed PDF exports dismissible

If ExportReportsToPDF fails after the optimistic PREPARING state is shown, this clears the Onyx entry instead of replacing it with FAILED. ExportDownloadStatusModal keeps rendering the last defined export via usePreviousDefined, so the user remains stuck in the non-dismissible “Preparing download...” state with no failure UI or close path. Please write a failed state here so the modal can recover.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated to:

    const failureData: AnyOnyxUpdate[] = [
        {
            onyxMethod: Onyx.METHOD.SET,
            key: onyxKey,
            value: {state: CONST.EXPORT_DOWNLOAD.STATE.FAILED},
        },
    ];

fileDownload(translate, downloadURL);
}, [isReady, downloadURL, translate, shouldSendFromConcierge]);
downloadFile();
// eslint-disable-next-line react-hooks/exhaustive-deps

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

❌ CONSISTENCY-5 (docs)

The eslint-disable-next-line react-hooks/exhaustive-deps comment lacks a justification explaining why certain dependencies are intentionally omitted from the dependency array. The downloadFile function is called inside the effect but excluded from the deps -- reviewers and future maintainers need to understand why.

Add a comment explaining the reason, for example:

// We intentionally omit downloadFile from deps to avoid re-triggering the download
// when its closure variables (environment, encryptedAuthToken, etc.) change.
// The download should only fire when the export transitions to ready.
// eslint-disable-next-line react-hooks/exhaustive-deps
}, [isReady, fileName, shouldSendFromConcierge]);

Reviewed at: 43857b1 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Added comment

@trjExpensify

Copy link
Copy Markdown
Contributor

Is this ready to be tested on an adhoc build or does it need the backend PR you're alluding to first?

@truph01

truph01 commented Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

Is this ready to be tested on an adhoc build or does it need the backend PR you're alluding to first?

It needs the backend's PR.

cc @mollfpr How's BE PR going?

@truph01

truph01 commented Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@truph01

truph01 commented Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

@truph01 please update the records in your checklist

@daledah I've added videos in web platform.

@daledah daledah left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The changes LGTM and work well on the web. For native, @mollfpr could you please verify that everything works as expected before we merge this?

@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 Jun 17, 2026

Copy link
Copy Markdown
Contributor

Web and Android look good!

@trjExpensify all yours to have a look 🙌

trjExpensify
trjExpensify previously approved these changes Jun 17, 2026

@trjExpensify trjExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Core PR for a WN project. 👍

@truph01

truph01 commented Jun 18, 2026

Copy link
Copy Markdown
Contributor Author

@mollfpr All yours!

@mollfpr

mollfpr commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

@truph01 could you resolve the conflict when you available? Thanks!

@truph01

This comment was marked as duplicate.

1 similar comment
@truph01

truph01 commented Jun 19, 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: cc7cf17f90

ℹ️ 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/hooks/useSearchBulkActions.ts Outdated
await exportReportToPDF({reportID: reportIDForPDF});
setPdfReportID(reportIDForPDF);
setIsPdfModalVisible(true);
const exportID = exportReportsToPDF(selectedReportIDs.map(Number));

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 Preserve report IDs as strings when exporting PDFs

For multi-report PDF downloads, converting selectedReportIDs with Number can corrupt real report IDs because they are stored as strings and often exceed JavaScript's safe integer range. For example, a report ID like 8759152536123291182 is rounded to 8759152536123292000 before being JSON-stringified, so the backend is asked to export non-existent or wrong reports whenever selected IDs are larger than Number.MAX_SAFE_INTEGER.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Resolved

@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 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM! Tested well!

@mollfpr mollfpr requested a review from trjExpensify June 19, 2026 06:11
@mollfpr

mollfpr commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Re-request @trjExpensify review, and @daledah, could you update the reviewer checklist? It seems we have updated the reviewer checklist and have a different count.

@daledah

daledah commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

@mollfpr sure, i'm checking again

@mollfpr

mollfpr commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

@daledah any update on the checklist?

@daledah

daledah commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

@mollfpr I've updated the checklist and reviewed the code changes again. Everything LGTM.

@trjExpensify trjExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Re-approve. 👍

@mollfpr mollfpr merged commit df28b54 into Expensify:main Jun 19, 2026
36 of 38 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

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.

4 participants