Fix: Zero amount not displayed in receipt and expense details for distance expense #58649

ryntgh · 2025-03-18T15:31:22Z

Explanation of Change

Fixed Issues

$ #58478
PROPOSAL: #58478 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Go to workspace settings > enable distance rate
Change the rate to 0.0001
Go to workspace chat
Create a distance expense with the following waypoints:
65, Pappammal Koil, Vaithikuppam, Puducherry, India & 67, Pappammal Koil, Vaithikuppam, Puducherry, India.
Note in confirmation page and in expense preview 0.00 amount is shown
Open the expense
Verify that the amount displayed on MoneyRequestView is 0.00
Tap the receipt
Verify that the receipt displays 0.00 as the amount

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 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 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-Native.mp4

Android: mWeb Chrome

Android-mWeb.mp4

iOS: Native

iOS-Native.mp4

iOS: mWeb Safari

iOS-mWeb.mp4

MacOS: Chrome / Safari

MacOS-Chrome.mp4

MacOS: Desktop

MacOS-Desktop.mp4

…tance expense

github-actions · 2025-03-18T15:31:34Z

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

ryntgh · 2025-03-18T15:32:19Z

I have read the CLA Document and I hereby sign the CLA

melvin-bot · 2025-03-18T15:44:13Z

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

Ollyws · 2025-03-19T19:56:28Z

I'm just wondering, as per some comments in the thread if the $0.00 should be shown in all cases when the transactionAmount is returned as $0, as this will display $0.00 when the route is still pending (if you make a request while offline for example). Any idea @rlinoz?

rlinoz · 2025-03-19T20:19:13Z

If we don't have the amount I think we should display as empty.

ryntgh · 2025-03-20T04:30:33Z

The PR has been updated to cover that case

Ollyws · 2025-03-20T10:41:03Z

src/components/ReportActionItem/MoneyRequestView.tsx

+    const hasRoute = hasRouteTransactionUtils(transactionBackup ?? transaction, isDistanceRequest);
+    const pendingTransactionAmount = transaction?.pendingAction && isDistanceRequest && !hasRoute ? undefined : transactionAmount;
+    const formattedTransactionAmount =
+        pendingTransactionAmount !== null && pendingTransactionAmount !== undefined ? convertToDisplayString(pendingTransactionAmount, transactionCurrency) : '';


Could we define pendingTransactionAmount !== null && pendingTransactionAmount !== undefined in a seperate const to avoid repeating ourselves? Thanks

Sure, I've updated the code to separate the pending amount check into a new const

Ollyws · 2025-03-20T17:07:20Z

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: Native
- Android: mWeb Chrome
- iOS: Native
- 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 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: Native

01_Android_Native.mp4

Android: mWeb Chrome

02_Android_Chrome.mp4

iOS: Native

03_iOS_Native.mp4

iOS: mWeb Safari

04_iOS_Safari.mp4

MacOS: Chrome / Safari

05_MacOS_Chrome.mp4

MacOS: Desktop

06_MacOS_Desktop.mp4

Ollyws · 2025-03-20T17:18:20Z

@ryntgh Something I just noticed is that the amount doesn't show up if we change it while the request is pending:

Screen.Recording.2025-03-20.at.17.15.51.mov

ryntgh · 2025-03-21T02:07:14Z

Something I just noticed is that the amount doesn't show up if we change it while the request is pending

Ah yeah, you're right! I've updated the code to cover that edge case. Could you please check it again? Thanks

Ollyws

Thanks! LGTM.

rlinoz · 2025-03-21T15:02:35Z

I think we don't want to show $0 when the SmartScan fails either

This branch:

Staging:

…tance expense

ryntgh · 2025-03-21T18:33:00Z

I think we don't want to show $0 when the SmartScan fails either

PR updated! Let me know if I missed anything else

rlinoz · 2025-03-21T18:37:08Z

@ryntgh I will review now, but do you mind merging main? I think some lint issues are fixed

ryntgh · 2025-03-21T18:43:56Z

Sure, I've merged latest main

rlinoz

Thanks!

OSBotify · 2025-03-24T14:18:03Z

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

github-actions · 2025-03-24T21:30:27Z

🚀 Deployed to staging by https://github.com/rlinoz in version: 9.1.18-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	cancelled 🔪
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	cancelled 🔪
🍎🔄 iOS HybridApp 🍎🔄	cancelled 🔪

github-actions · 2025-03-26T05:04:11Z

🚀 Deployed to production by https://github.com/cristipaval in version: 9.1.18-4 🚀

platform	result
🤖 android 🤖	true ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	failure ❌

Fix: Zero amount not displayed in receipt and expense details for dis…

aecb167

…tance expense

CLABotify added a commit to Expensify/CLA that referenced this pull request Mar 18, 2025

@ryntgh has signed the CLA in Expensify/App#58649

437e19f

ryntgh marked this pull request as ready for review March 18, 2025 15:44

ryntgh requested a review from a team as a code owner March 18, 2025 15:44

melvin-bot bot requested review from Ollyws and removed request for a team March 18, 2025 15:44

fix: pending transaction amount displays as 0

db466db

fix: pending transaction amount displays as 0

58c7660

Ollyws reviewed Mar 20, 2025

View reviewed changes

fix: pending amount check

163f406

ryntgh added 2 commits March 21, 2025 08:58

ESLint fix

99607d9

fix: amount is not updated when pending

07a834c

Ollyws approved these changes Mar 21, 2025

View reviewed changes

melvin-bot bot requested a review from rlinoz March 21, 2025 14:11

fix: Zero amount not displayed in receipt and expense details for dis…

0cf2267

…tance expense

Merge branch 'main' into issue-58478

0f56eeb

rlinoz approved these changes Mar 24, 2025

View reviewed changes

rlinoz merged commit 5e67119 into Expensify:main Mar 24, 2025
15 checks passed

github-actions bot mentioned this pull request Mar 24, 2025

Deploy Checklist: New Expensify 2025-03-24 #59011

Closed

48 tasks

techievivek mentioned this pull request Mar 25, 2025

[$250] Distance expense-Route exceeds maximum distance limitation error after adding a stop offline #59028

Open

8 tasks

melvin-bot bot mentioned this pull request Mar 26, 2025

[Due for payment 2025-04-02] [$250] Distance - Zero amount not displayed in receipt and expense details for distance expense #58478

Open

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix: Zero amount not displayed in receipt and expense details for distance expense #58649

Fix: Zero amount not displayed in receipt and expense details for distance expense #58649

ryntgh commented Mar 18, 2025

github-actions bot commented Mar 18, 2025 •

edited

Loading

ryntgh commented Mar 18, 2025

melvin-bot bot commented Mar 18, 2025

Ollyws commented Mar 19, 2025

rlinoz commented Mar 19, 2025

ryntgh commented Mar 20, 2025

Ollyws Mar 20, 2025

ryntgh Mar 20, 2025

Ollyws commented Mar 20, 2025

Ollyws commented Mar 20, 2025

ryntgh commented Mar 21, 2025

Ollyws left a comment

rlinoz commented Mar 21, 2025

ryntgh commented Mar 21, 2025

rlinoz commented Mar 21, 2025

ryntgh commented Mar 21, 2025

rlinoz left a comment

OSBotify commented Mar 24, 2025

github-actions bot commented Mar 24, 2025

github-actions bot commented Mar 26, 2025

Fix: Zero amount not displayed in receipt and expense details for distance expense #58649

Fix: Zero amount not displayed in receipt and expense details for distance expense #58649

Conversation

ryntgh commented Mar 18, 2025

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

github-actions bot commented Mar 18, 2025 • edited Loading

ryntgh commented Mar 18, 2025

melvin-bot bot commented Mar 18, 2025

Ollyws commented Mar 19, 2025

rlinoz commented Mar 19, 2025

ryntgh commented Mar 20, 2025

Ollyws Mar 20, 2025

Choose a reason for hiding this comment

ryntgh Mar 20, 2025

Choose a reason for hiding this comment

Ollyws commented Mar 20, 2025

Reviewer Checklist

Screenshots/Videos

Ollyws commented Mar 20, 2025

ryntgh commented Mar 21, 2025

Ollyws left a comment

Choose a reason for hiding this comment

rlinoz commented Mar 21, 2025

ryntgh commented Mar 21, 2025

rlinoz commented Mar 21, 2025

ryntgh commented Mar 21, 2025

rlinoz left a comment

Choose a reason for hiding this comment

OSBotify commented Mar 24, 2025

github-actions bot commented Mar 24, 2025

github-actions bot commented Mar 26, 2025

github-actions bot commented Mar 18, 2025 •

edited

Loading