Skip to content

fix: Update empty receipt section in the expense RHP#79545

Merged
NikkiWines merged 4 commits intoExpensify:mainfrom
nkdengineer:fix/79189
Jan 27, 2026
Merged

fix: Update empty receipt section in the expense RHP#79545
NikkiWines merged 4 commits intoExpensify:mainfrom
nkdengineer:fix/79189

Conversation

@nkdengineer
Copy link
Contributor

Explanation of Change

fix: Update empty receipt section in the expense RHP

Fixed Issues

$ #79189
PROPOSAL: #79189 (comment)

Tests

  1. Open a workspace chat
  2. Create two expenses without receipt
  3. Open expense report
  4. Click on any transaction
  5. Verify that the receipt alternative method is displayed at the bottom of the empty receipt view
  • Verify that no errors appear in the JS console

Offline tests

Same

QA Steps

Same as test

  • 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 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 Screenshot 2026-01-14 at 16 55 35
Android: mWeb Chrome Screenshot 2026-01-14 at 16 54 53
iOS: Native Screenshot 2026-01-14 at 16 56 30
iOS: mWeb Safari Screenshot 2026-01-14 at 16 54 17
MacOS: Chrome / Safari Screenshot 2026-01-14 at 16 52 56

@melvin-bot
Copy link

melvin-bot bot commented Jan 14, 2026

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

@nkdengineer nkdengineer marked this pull request as ready for review January 14, 2026 11:03
@nkdengineer nkdengineer requested review from a team as code owners January 14, 2026 11:03
@melvin-bot
Copy link

melvin-bot bot commented Jan 14, 2026

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

@melvin-bot melvin-bot bot removed request for a team and trjExpensify January 14, 2026 11:03
Copy link

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

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: 51d7927039

ℹ️ 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 +108 to +110
</View>
</View>
{isDisplayedInWideRHP && !disabled && <ReceiptAlternativeMethods />}

Choose a reason for hiding this comment

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

P2 Badge Keep alternative-method links out of the receipt pressable

In the wide RHP flow, ReceiptEmptyState is rendered as a Pressable that navigates to the receipt upload on press, and ReceiptAlternativeMethods (which contains <a> links) is now nested inside that pressable. On web/desktop, click events bubble, so clicking “Download the app”/mailto/sms links will also trigger the parent onPress and immediately navigate to the scan/receipt route, making those links effectively unusable in that context. Consider moving ReceiptAlternativeMethods outside the pressable or disabling the parent’s interaction for that sub-tree (e.g., pointerEvents="box-none" or a non-pressable wrapper) so link clicks don’t fire the upload navigation.

Useful? React with 👍 / 👎.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think this is correct, shouldn't we do something like:

{isDisplayedInWideRHP && !disabled && (
    <View onClick={(e) => e.stopPropagation()}>
        <ReceiptAlternativeMethods />
    </View>
)}

Copy link
Contributor

Choose a reason for hiding this comment

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

From testing, pressing the links inside ReceiptAlternativeMethods doesn't bubble to the parent Pressable, so wrapping with stopPropagation is unnecessary. Either way looks fine to me.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, great! Thanks for confirming 🙌

@dannymcclain
Copy link
Contributor

Let me know when this is ready for @Expensify/design to review and I will make a build 👍

@DylanDylann
Copy link
Contributor

@dannymcclain This is ready for @Expensify/design to review

@DylanDylann
Copy link
Contributor

The code looks fine to me. Wating for the design team to review before completing the checklist

@DylanDylann
Copy link
Contributor

DylanDylann commented Jan 15, 2026

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 Screenshot 2026-01-26 at 14 20 19
Android: mWeb Chrome
Screen.Recording.2026-01-26.at.14.19.13.mov
iOS: HybridApp Screenshot 2026-01-26 at 14 20 14
iOS: mWeb Safari
Screen.Recording.2026-01-26.at.14.18.52.mov
MacOS: Chrome / Safari Screenshot 2026-01-26 at 14 11 00

@github-actions
Copy link
Contributor

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

@github-actions

This comment has been minimized.

@dannymcclain
Copy link
Contributor

Looking pretty good! Here are a couple nitpicky comments:

We can remove this 4px of padding:
CleanShot 2026-01-15 at 08 54 04@2x

We need to add 8px of padding beneath the "other ways" block:
CleanShot 2026-01-15 at 08 54 54@2x

@DylanDylann
Copy link
Contributor

@nkdengineer Kindly bump

@nkdengineer
Copy link
Contributor Author

@dannymcclain I updated.

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

@dannymcclain
Copy link
Contributor

Latest build is looking good to me. cc @dubielzyk-expensify too.

One tiny thing, can we remove this period?
CleanShot 2026-01-19 at 11 15 37@2x

I noticed our regular upload message (during scan) doesn't use punctuation, so I don't think we need it here either.

@nkdengineer
Copy link
Contributor Author

@dannymcclain I updated.

@dubielzyk-expensify
Copy link
Contributor

Adhoc branch looking great to me 👍

@DylanDylann
Copy link
Contributor

@dubielzyk-expensify @dannymcclain When clicking on the empty receipt, a similar modal will be displayed as a small RHP. Is it okay?

Screen.Recording.2026-01-20.at.10.55.26.mov

@dubielzyk-expensify
Copy link
Contributor

That feels a bit duplicative to me. Is that what it was like before? Part of me just wonders if we should directly show the OS dialog as those screen are now practically the same. Mobile goes straight to camera so I'd expect this to be equally direct.

Keen to hear what @dannymcclain thinks

@DylanDylann
Copy link
Contributor

Part of me just wonders if we should directly show the OS dialog as those screen are now practically the same. Mobile goes straight to camera so I'd expect this to be equally direct.

I have same thought with you

@trjExpensify
Copy link
Contributor

Yeah, I agree with you @dubielzyk-expensify. Feels unnecessary with the empty state.

@dannymcclain
Copy link
Contributor

Totally agree!

@dubielzyk-expensify
Copy link
Contributor

Cool. Let's change to open the system file picker dialog then instead. It'd also allow for drag n drop anyways so we got both methods covered then 👍

@trjExpensify
Copy link
Contributor

@nkdengineer you good to make that change?

@nkdengineer
Copy link
Contributor Author

@trjExpensify Handle the picker here is complex so I think we can handle it as a follow-up after we merge this PR.

@nkdengineer
Copy link
Contributor Author

@trjExpensify Any thoughts on my comment above?

@trjExpensify
Copy link
Contributor

I'm cool to separate the PRs for it, we should do it as a fast follower though. 👍

@melvin-bot melvin-bot bot requested a review from NikkiWines January 26, 2026 07:20
Comment on lines +108 to +110
</View>
</View>
{isDisplayedInWideRHP && !disabled && <ReceiptAlternativeMethods />}
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this is correct, shouldn't we do something like:

{isDisplayedInWideRHP && !disabled && (
    <View onClick={(e) => e.stopPropagation()}>
        <ReceiptAlternativeMethods />
    </View>
)}

@trjExpensify
Copy link
Contributor

@nkdengineer over to you!

Copy link
Contributor

@NikkiWines NikkiWines left a comment

Choose a reason for hiding this comment

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

👍

@NikkiWines NikkiWines merged commit 30d83c7 into Expensify:main Jan 27, 2026
34 checks passed
@OSBotify
Copy link
Contributor

✋ 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

🚀 Deployed to staging by https://github.com/NikkiWines in version: 9.3.10-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.10-6 🚀

platform result
🕸 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.

7 participants