Skip to content

fix: reduce the PDF download steps by one click#72846

Merged
cristipaval merged 10 commits intoExpensify:mainfrom
daledah:fix/72035
Nov 3, 2025
Merged

fix: reduce the PDF download steps by one click#72846
cristipaval merged 10 commits intoExpensify:mainfrom
daledah:fix/72035

Conversation

@daledah
Copy link
Contributor

@daledah daledah commented Oct 17, 2025

Explanation of Change

Fixed Issues

$ #72035
PROPOSAL: #72035 (comment)

Tests

  1. Create a report
  2. Add a couple of expenses to it
  3. Click More > Download as PDF
  4. Click Download
  5. Verify that: The report is automatically downloaded after loading.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Create a report
  2. Add a couple of expenses to it
  3. Click More > Download as PDF
  4. Click Download
  5. Verify that: The report is automatically downloaded after loading.
  • 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
    • MacOS: Desktop
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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.mov
Android: mWeb Chrome
Screen.Recording.2025-10-17.at.15.50.57.mov
iOS: Native
ios.mov
iOS: mWeb Safari
Screen.Recording.2025-10-17.at.15.56.43.mov
MacOS: Chrome / Safari
Screen.Recording.2025-10-17.at.15.59.22.mov
MacOS: Desktop
Screen.Recording.2025-10-17.at.16.00.28.mov

@codecov
Copy link

codecov bot commented Oct 17, 2025

Codecov Report

❌ Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/components/MoneyReportHeader.tsx 0.00% 6 Missing ⚠️
Files with missing lines Coverage Δ
src/CONST/index.ts 85.71% <ø> (+1.90%) ⬆️
src/components/MoneyReportHeader.tsx 0.18% <0.00%> (+<0.01%) ⬆️

... and 276 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@daledah daledah marked this pull request as ready for review October 17, 2025 09:05
@daledah daledah requested a review from a team as a code owner October 17, 2025 09:05
@melvin-bot melvin-bot bot requested review from alitoshmatov and removed request for a team October 17, 2025 09:05
@melvin-bot
Copy link

melvin-bot bot commented Oct 17, 2025

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

@dannymcclain
Copy link
Contributor

@dubielzyk-expensify does this alignment for the spinner look right to you? It doesn't feel quite as centered as you have it laid out here. Could just be my eyes playing tricks though—@daledah can you double check?
CleanShot 2025-10-18 at 11 11 59@2x

For iOS, why doesn't this modal have a title like it does on desktop/web? And why does it change?
CleanShot 2025-10-18 at 11 14 58@2x
CleanShot 2025-10-18 at 11 15 14@2x

Same question for mobile web, why does the modal change part way through?
CleanShot 2025-10-18 at 11 16 34@2x

CleanShot 2025-10-18 at 11 16 58@2x

@dubielzyk-expensify
Copy link
Contributor

Agree with everything you're saying Danny. Doesn't look vertically centered:

CleanShot 2025-10-20 at 10 33 45@2x

@JmillsExpensify
Copy link
Contributor

@alitoshmatov please help us with a PR review when you're on. We'd like to prioritize getting this improvement to production.

@alitoshmatov
Copy link
Contributor

Same question for mobile web, why does the modal change part way through?

@daledah Is this because downloading is also taking a little bit time.

May be we should combine both waiting for file and downloading states into one, and show single message in both cases here:

const messagePDF = useMemo(() => {
if (!reportPDFFilename) {
return translate('reportDetailsPage.waitForPDF');
}
if (reportPDFFilename === CONST.REPORT_DETAILS_MENU_ITEM.ERROR) {
return translate('reportDetailsPage.errorPDF');
}
return translate('reportDetailsPage.generatedPDF');
}, [reportPDFFilename, translate]);

@daledah
Copy link
Contributor Author

daledah commented Oct 22, 2025

@alitoshmatov I updated using your suggestions.

For iOS, why doesn't this modal have a title like it does on desktop/web? And why does it change?

Currently I can't find the RCA for this, but the modal component cuts off its contents so the header is not shown. I'll take a deeper look into this. But IMO it's a out-of-scope bug for this PR.

@trjExpensify
Copy link
Contributor

@daledah are you saying that the iOS modal title bug is present in other modals on production?

@trjExpensify
Copy link
Contributor

Bump @daledah!

@situchan
Copy link
Contributor

I'd be happy to review this since @alitoshmatov is OOO starting today

@trjExpensify
Copy link
Contributor

Yes please!

@trjExpensify trjExpensify requested a review from situchan October 27, 2025 18:57
@melvin-bot
Copy link

melvin-bot bot commented Oct 28, 2025

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. If you want to automatically generate translations for other locales, you can run the Generate static translations GitHub workflow.

Please look at the code and make sure there are no malicious changes before running the workflow.

If you have the K2 extension, you can simply click: [this button]

@daledah
Copy link
Contributor Author

daledah commented Oct 28, 2025

@trjExpensify Fixed the header not showing, turns out it's because of incorrect stylings 😅

@situchan
Copy link
Contributor

Unit Tests failing

@situchan
Copy link
Contributor

I am being redirected to expensify.com.dev
Is it expected?

web.mov

@daledah
Copy link
Contributor Author

daledah commented Oct 30, 2025

I'm checking now

@melvin-bot
Copy link

melvin-bot bot commented Oct 30, 2025

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

@daledah
Copy link
Contributor Author

daledah commented Oct 30, 2025

I am being redirected to expensify.com.dev Is it expected?

web.mov

@situchan This is expected when testing on the dev branch as logic here

App/src/libs/actions/Report.ts

Lines 4921 to 4927 in 13a0e11

function downloadReportPDF(fileName: string, reportName: string) {
const baseURL = addTrailingForwardSlash(getOldDotURLFromEnvironment(environment));
const downloadFileName = `${reportName}.pdf`;
setDownload(fileName, true);
const pdfURL = `${baseURL}secure?secureType=pdfreport&filename=${encodeURIComponent(fileName)}&downloadName=${encodeURIComponent(downloadFileName)}&email=${encodeURIComponent(
currentUserEmail ?? '',
)}`;

@daledah
Copy link
Contributor Author

daledah commented Oct 30, 2025

@situchan Looks like the PDF download link is having problems with the dev environment. After changing to use staging environment, it works well

Screenshot 2025-10-30 at 14 54 10
ios.mov

@daledah
Copy link
Contributor Author

daledah commented Oct 30, 2025

I am still seeing missing header on native.

@situchan i updated the videos on native

@situchan
Copy link
Contributor

situchan commented Oct 30, 2025

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (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 verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • 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
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
android.mov
Android: mWeb Chrome
mchrome.mov
iOS: HybridApp
ios.mov
iOS: mWeb Safari
msafari.mov
MacOS: Chrome / Safari
web.mov
MacOS: Desktop

@situchan
Copy link
Contributor

@trjExpensify can you please generate adhoc build here?
As download is not working correctly in dev env, wanna test adhoc build.

@trjExpensify
Copy link
Contributor

On it

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
Built from App PR #72846.

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/72846/index.html https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/72846/index.html
Android iOS
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/72846/NewExpensify.dmg https://72846.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

@dannymcclain
Copy link
Contributor

Doesn't seem to be working on that build for me.

@trjExpensify
Copy link
Contributor

@daledah, what's your next step here?

@daledah
Copy link
Contributor Author

daledah commented Oct 31, 2025

@trjExpensify i resolved all comments. Waiting for the next review from @situchan

@situchan
Copy link
Contributor

Doesn't seem to be working on that build for me.

I think the question is about this

@situchan
Copy link
Contributor

Doesn't seem to be working on that build for me.

@dannymcclain which platforms have you tested on? Can you please share video?

I tested on android native, android chrome, ios safari and worked fine.

@dannymcclain
Copy link
Contributor

Looks like Chrome is the bugger here for some reason. Works fine for me on Safari?

Chrome
It spins like it's making the PDF or something, but nothing ever happens. The modal just goes away.

CleanShot.2025-10-31.at.12.41.52.mp4

Safari
Works so quickly I don't even see the modal haha. I didn't expect the new tab to pop open, but it properly closes the tab and everything works how I would expect, so it seems good to me.

CleanShot.2025-10-31.at.12.43.10.mp4

@situchan
Copy link
Contributor

@dannymcclain maybe because it's adhoc url. Hopefully work fine on staging / production

Screenshot 2025-10-31 at 11 50 24 PM

Please allow here

Comment on lines +1483 to +1486
<ActivityIndicator
size={CONST.ACTIVITY_INDICATOR_SIZE.SMALL}
color={theme.textSupporting}
style={styles.ml3}
Copy link
Contributor

Choose a reason for hiding this comment

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

When failed to generate pdf, still shows loading indicator. Hope this would be fine.

@melvin-bot melvin-bot bot requested a review from cristipaval October 31, 2025 17:56
@dannymcclain
Copy link
Contributor

maybe because it's adhoc url. Hopefully work fine on staging / production
Please allow here

Ah ha! Thank you so much for that—didn't even see that it blocked a pop up 🤦‍♂️

Once I allowed from there it worked perfectly 👍

@dubielzyk-expensify
Copy link
Contributor

Dialog looks good from my eyes 👍

@cristipaval cristipaval merged commit 8c53c50 into Expensify:main Nov 3, 2025
29 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Nov 3, 2025

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

OSBotify commented Nov 3, 2025

🚀 Deployed to staging by https://github.com/cristipaval in version: 9.2.43-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented Nov 4, 2025

🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.43-2 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

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.

9 participants