[CP Staging] Revert "fix: Confirm page shows Amount field with 0.00 amount when receipt is scanning v2" by srikarparsi · Pull Request #85256 · Expensify/App

srikarparsi · 2026-03-13T17:17:03Z

Test:

Go to a 1:1 DM or Group
Create a split expense with only amount
Ensure a Receipt is missing error does not show up

…ceipt is scanning v2"

melvin-bot · 2026-03-13T17:23:09Z

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

Beamanator · 2026-03-13T17:24:07Z

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
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: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7b05dcbd93

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-03-13T17:34:04Z

src/components/MoneyRequestConfirmationList.tsx

-    } else if (isScanning(transaction)) {
-        formattedAmount = translate('iou.receiptStatusTitle');
-    }
+    const formattedAmount = isDistanceRequestWithPendingRoute ? '' : convertToDisplayString(amountToBeUsed, isDistanceRequest ? currency : iouCurrencyCode);


Restore scanning label for pending receipt amounts

This change always formats the draft amount as currency, so a scan request that is still in SCAN_READY/SCANNING now shows 0.00 in the confirmation Amount field until OCR finishes. In that state the transaction has no real extracted amount yet, so displaying a numeric value is misleading and regresses the prior behavior that showed iou.receiptStatusTitle for pending scans; users can incorrectly assume the parsed amount is zero while the receipt is still processing.

Useful? React with 👍 / 👎.

This is correct. That said, showing the not found page is worse than the 0.00 amount while scanning a receipt, so the straight revert still makes sense.

…vert-81156-fix/80287 [CP Staging] Revert "fix: Confirm page shows Amount field with 0.00 amount when receipt is scanning v2" (cherry picked from commit 69ab566) (cherry-picked to staging by luacmartins)

OSBotify · 2026-03-13T17:49:55Z

✋ 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 · 2026-03-13T18:22:39Z

🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.3.37-4 🚀

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

github-actions · 2026-03-13T18:25:31Z

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

github-actions · 2026-03-13T18:30:38Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-69ab566-33e885e-3901d8386fd4ba38cdedcdf9110dd0b1dcaae25d/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-69ab566-33e885e-05b16eafb89b1a973362f78211a928a024e389f9/index.html

Web 🕸️
https://85256.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-16T10:08:43Z

🚀 Deployed to production by https://github.com/cristipaval in version: 9.3.37-10 🚀

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

OSBotify · 2026-03-16T10:33:47Z

🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.3.38-0 🚀

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

OSBotify · 2026-03-17T11:29:34Z

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

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

Revert "fix: Confirm page shows Amount field with 0.00 amount when re…

7b05dcb

…ceipt is scanning v2"

melvin-bot bot assigned srikarparsi Mar 13, 2026

srikarparsi marked this pull request as ready for review March 13, 2026 17:22

srikarparsi requested review from a team as code owners March 13, 2026 17:22

melvin-bot bot requested review from Gonals and joekaufmanexpensify and removed request for a team March 13, 2026 17:22

Beamanator approved these changes Mar 13, 2026

View reviewed changes

srikarparsi changed the title ~~Revert "fix: Confirm page shows Amount field with 0.00 amount when receipt is scanning v2"~~ [CP Staging] Revert "fix: Confirm page shows Amount field with 0.00 amount when receipt is scanning v2" Mar 13, 2026

chatgpt-codex-connector bot reviewed Mar 13, 2026

View reviewed changes

luacmartins approved these changes Mar 13, 2026

View reviewed changes

srikarparsi merged commit 69ab566 into main Mar 13, 2026
48 of 54 checks passed

srikarparsi deleted the revert-82672-revert-82403-revert-81156-fix/80287 branch March 13, 2026 17:41

OSBotify added the CP Staging marks PRs that have been CP'd to staging label Mar 13, 2026

OSBotify mentioned this pull request Mar 13, 2026

Deploy Checklist: New Expensify 2026-03-12 #85146

Closed

87 tasks

srikarparsi mentioned this pull request Mar 13, 2026

Split Expense - The error “Receipt is missing” is displayed when performing a split. #85152

Closed

7 tasks

MelvinBot mentioned this pull request Mar 13, 2026

Expense-Creating distance manual expense shows unexpected error. #85173

Closed

7 tasks

nkdengineer mentioned this pull request Mar 17, 2026

fix: Confirm page shows Amount field with 0.00 amount when receipt is scanning v3 #85513

Open

53 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CP Staging] Revert "fix: Confirm page shows Amount field with 0.00 amount when receipt is scanning v2"#85256

[CP Staging] Revert "fix: Confirm page shows Amount field with 0.00 amount when receipt is scanning v2"#85256
srikarparsi merged 1 commit intomainfrom
revert-82672-revert-82403-revert-81156-fix/80287

srikarparsi commented Mar 13, 2026 •

edited

Loading

Uh oh!

melvin-bot bot commented Mar 13, 2026

Uh oh!

Beamanator commented Mar 13, 2026 •

edited

Loading

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Mar 13, 2026

Uh oh!

luacmartins Mar 13, 2026

Uh oh!

Uh oh!

OSBotify commented Mar 13, 2026

Uh oh!

OSBotify commented Mar 13, 2026

Uh oh!

github-actions bot commented Mar 13, 2026

Uh oh!

github-actions bot commented Mar 13, 2026

Uh oh!

OSBotify commented Mar 16, 2026

Uh oh!

OSBotify commented Mar 16, 2026

Uh oh!

OSBotify commented Mar 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

srikarparsi commented Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

melvin-bot bot commented Mar 13, 2026

Uh oh!

Beamanator commented Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 13, 2026

Choose a reason for hiding this comment

Uh oh!

luacmartins Mar 13, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Mar 13, 2026

Uh oh!

OSBotify commented Mar 13, 2026

Uh oh!

github-actions bot commented Mar 13, 2026

Uh oh!

github-actions bot commented Mar 13, 2026

Uh oh!

OSBotify commented Mar 16, 2026

Uh oh!

OSBotify commented Mar 16, 2026

Uh oh!

OSBotify commented Mar 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

srikarparsi commented Mar 13, 2026 •

edited

Loading

Beamanator commented Mar 13, 2026 •

edited

Loading