Skip to content

Display new UI for alternate methods of scanning receipts#71340

Merged
inimaga merged 38 commits intoExpensify:mainfrom
ShridharGoel:alternateMethods
Oct 7, 2025
Merged

Display new UI for alternate methods of scanning receipts#71340
inimaga merged 38 commits intoExpensify:mainfrom
ShridharGoel:alternateMethods

Conversation

@ShridharGoel
Copy link
Contributor

@ShridharGoel ShridharGoel commented Sep 25, 2025

Explanation of Change

Display new UI for alternate methods of scanning receipts.

Fixed Issues

$ #70693
PROPOSAL: #70693 (comment)

Tests

Update Onyx data via console to simulate the different scenarios (else you can use different accounts which have the scenarios):

1. No Mobile App • No Phone Number

['nvp_lastAndroidLogin','nvp_lastiPhoneLogin','nvp_lastECashAndroidLogin','nvp_lastECashIOSLogin'].forEach((key) => Onyx.merge(key, null));
Onyx.set('loginList', {});
Onyx.merge('session', {email: 'user@example.com'});

Expectation:

  • Download the app to scan from your phone
  • Forward receipts to receipts@expensify.com
  • Add your number to text receipts to 47777

2. Mobile App Logged In • No Phone Number

['nvp_lastAndroidLogin','nvp_lastiPhoneLogin','nvp_lastECashAndroidLogin','nvp_lastECashIOSLogin'].forEach((key) => Onyx.merge(key, null));
Onyx.set('loginList', {});
Onyx.merge('session', {email: 'user@example.com'});
Onyx.merge('nvp_lastAndroidLogin', {lastVisited: new Date().toISOString()});

Expectation:

3. No Mobile App • Phone Number Present

['nvp_lastAndroidLogin','nvp_lastiPhoneLogin','nvp_lastECashAndroidLogin','nvp_lastECashIOSLogin'].forEach((key) => Onyx.merge(key, null));
Onyx.set('loginList', {'+12223334444@expensify.sms': {partnerUserID: '+12223334444@expensify.sms'}});
Onyx.merge('session', {email: 'user@example.com'});

Expectation:

  • Download the app to scan from your phone
  • Forward receipts to receipts@expensify.com
  • Text receipts to 47777 (US numbers only)

4. Mobile App Logged In • Phone Number Present

['nvp_lastAndroidLogin','nvp_lastiPhoneLogin','nvp_lastECashAndroidLogin','nvp_lastECashIOSLogin'].forEach((key) => Onyx.merge(key, null));
Onyx.set('loginList', {'+12223334444@expensify.sms': {partnerUserID: '+12223334444@expensify.sms'}});
Onyx.merge('session', {email: 'user@example.com'});
Onyx.merge('nvp_lastAndroidLogin', {lastVisited: new Date().toISOString()});

Expectation:

image

Offline tests

QA Steps

Scenario A – No mobile app • No phone number

  1. Sign in with an account that has only an email login and has never opened the mobile app.
    • New test accounts created on web fit this state by default.
  2. Navigate to Create expense → Scan.
  3. Verify the panel shows:
    • “Download the app to scan from your phone” link.
    • “Forward receipts to receipts@expensify.com”.
    • “Add your number to text receipts to 47777”.

Scenario B – Mobile app used • No phone number

  1. Install the Expensify mobile app on a device.
  2. Log in with the same email account from Scenario A.
  3. Return to the web/desktop app, refresh, open Create expense → Scan.
  4. Confirm the panel now shows exactly:

Scenario C – No mobile app • Phone number added

  1. Use an account that has not opened the mobile app.
  2. Go to Settings → Profile → Contact methods and add a phone number. Verify it’s confirmed (SMS code).
  3. Refresh the Scan tab.
  4. Confirm the panel shows:
    • “Download the app to scan from your phone”.
    • “Forward receipts to receipts@expensify.com”.
    • “Text receipts to 47777 (US numbers only)”.

Scenario D – Mobile app used • Phone number added

  1. Start from Scenario C’s account or any account with a verified phone number.
  2. Open the mobile app and sign in to mark the mobile login as active.
  3. Refresh the Scan tab on the desktop/web app.
  4. Confirm the panel shows exactly:
  • 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
    • 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 2025-10-07 at 1 08 15 PM
Android: mWeb Chrome
Screen.Recording.2025-10-07.at.1.10.06.PM.mov
iOS: Native
Simulator.Screen.Recording.-.iPhone.16.Plus.-.2025-10-07.at.13.13.01.mp4
iOS: mWeb Safari
Simulator.Screen.Recording.-.iPhone.16.Plus.-.2025-10-07.at.13.11.56.mp4
MacOS: Chrome / Safari
Screen.Recording.2025-10-07.at.1.10.41.PM.mov
Screenshot 2025-10-07 at 1 20 06 PM Screenshot 2025-10-07 at 1 19 50 PM Screenshot 2025-10-07 at 1 19 31 PM Screenshot 2025-10-07 at 1 19 14 PM
MacOS: Desktop
Screen.Recording.2025-10-07.at.1.15.23.PM.mov
Screenshot 2025-10-07 at 1 21 33 PM Screenshot 2025-10-07 at 1 21 16 PM Screenshot 2025-10-07 at 1 21 04 PM Screenshot 2025-10-07 at 1 20 43 PM

@codecov
Copy link

codecov bot commented Sep 25, 2025

Codecov Report

❌ Patch coverage is 84.31373% with 8 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...ages/iou/request/step/IOURequestStepScan/index.tsx 0.00% 7 Missing ⚠️
...TMLEngineProvider/HTMLRenderers/AnchorRenderer.tsx 0.00% 1 Missing ⚠️

📢 Thoughts on this report? Let us know!

@ShridharGoel ShridharGoel marked this pull request as ready for review September 26, 2025 20:00
@ShridharGoel ShridharGoel requested a review from a team as a code owner September 26, 2025 20:00
@melvin-bot melvin-bot bot requested review from parasharrajat and removed request for a team September 26, 2025 20:00
@melvin-bot
Copy link

melvin-bot bot commented Sep 26, 2025

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

Comment on lines 38 to 40
const shouldShowDownloadApp = !hasLoggedIntoMobileApp;
const shouldShowAddPhoneNumber = !hasPhoneNumber;
const shouldShowTextReceipts = hasPhoneNumber;
Copy link
Member

Choose a reason for hiding this comment

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

Remove extra variables and directly use the conditions.

import ONYXKEYS from '@src/ONYXKEYS';
import useOnyx from './useOnyx';

const useHasPhoneNumber = () => {
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
const useHasPhoneNumber = () => {
const useHasPhoneNumberLogin = () => {

Comment on lines 13 to 14
.map((login) => Str.removeSMSDomain(login))
.find((login) => Str.isValidE164Phone(login));
Copy link
Member

Choose a reason for hiding this comment

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

Can be done in one loop. Use .some

.map((login) => Str.removeSMSDomain(login))
.find((login) => Str.isValidE164Phone(login));

const smsLoginExists = Object.keys(loginList ?? {}).some((login) => Str.isSMSLogin(login));
Copy link
Member

Choose a reason for hiding this comment

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

How is it different from validPhoneInLoginList?

}),
},
receipt: {
alternativeMethodsTextReceipts: ({phoneNumber}: ReceiptAlternativeMethodsPhoneNumberParams) => `Text receipts to ${phoneNumber} (US numbers only)`,
Copy link
Member

Choose a reason for hiding this comment

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

Convert to a single string per sentence. Don't break into parts. Use RenderHTML component to render that whole sentense.

/>
</DragAndDropConsumer>
{!shouldHideDownloadAppBanner && <DownloadAppBanner onLayout={(e) => setDownloadAppBannerHeight(e.nativeEvent.layout.height)} />}
{!shouldHideAlternativeMethods && <ReceiptAlternativeMethods onLayout={(e) => setAlternativeMethodsHeight(e.nativeEvent.layout.height)} />}
Copy link
Member

Choose a reason for hiding this comment

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

DownloadAppBanner Remove this component if we are not using it anymore.

onLayout?: (event: LayoutChangeEvent) => void;
};

function ReceiptAlternativeMethods({onLayout}: ReceiptAlternativeMethodsProps) {
Copy link
Member

Choose a reason for hiding this comment

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

Add displayName

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Didn't get the usage of displayName here, can you clarify?

Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
function ReceiptAlternativeMethods({onLayout}: ReceiptAlternativeMethodsProps) {
ReceiptAlternativeMethods.displayName = "ReceiptAlternativeMethods";

Add this at the bottom of this component.

const {environmentURL} = useEnvironment();
const {translate} = useLocalize();
const {hasLoggedIntoMobileApp, isLastMobileAppLoginLoaded} = useHasLoggedIntoMobileApp();
const {hasPhoneNumberLogin, isLoaded: isPhoneNumberLoaded} = useHasPhoneNumberLogin();
Copy link
Member

Choose a reason for hiding this comment

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

Can you rename isLoaded to isPhoneNumberLoaded in the hook

Comment on lines -33 to -34
title={translate('common.getTheApp')}
subtitle={translate('common.scanReceiptsOnTheGo')}
Copy link
Member

Choose a reason for hiding this comment

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

let's remove these strings from the translations if not used in the app.

Comment on lines 1022 to 1030
alternativeMethodsTextReceipts: ({phoneNumber}: ReceiptAlternativeMethodsPhoneNumberParams) =>
`<muted-text-label>Text receipts to ${phoneNumber} (US numbers only)</muted-text-label>`,
alternativeMethodsForwardReceipts: ({email}: {email: string}) => `<muted-text-label>Forward receipts to <a href="mailto:${email}">${email}</a></muted-text-label>`,
alternativeMethodsDownloadApp: ({downloadUrl}: {downloadUrl: string}) => `<muted-text-label><a href="${downloadUrl}">Download the app</a> to scan from your phone</muted-text-label>`,
alternativeMethodsTitle: 'Other ways to add receipts:',
alternativeMethodsAddPhoneNumber: ({phoneNumber, contactMethodsUrl}: ReceiptAlternativeMethodsPhoneNumberParams & {contactMethodsUrl: string}) =>
`<muted-text-label><a href="${contactMethodsUrl}">Add your number</a> to text receipts to ${phoneNumber}</muted-text-label>`,
desktopSubtitleMultiple: 'or drag and drop them here',
desktopSubtitleSingle: 'or drag and drop them here',
Copy link
Member

Choose a reason for hiding this comment

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

Have you confirmed this on slack? Can you please add the slack discussion link in PR checklist

@parasharrajat
Copy link
Member

Please use meaningful commit messages.

} from './params';
import type {TranslationDeepObject} from './types';

type ReceiptAlternativeMethodsPhoneNumberParams = {
Copy link
Member

Choose a reason for hiding this comment

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

Move this type to params and import on each file.

@parasharrajat
Copy link
Member

@ShridharGoel please add QA steps and test steps. You can see other PRs for examples.

Also, fix the checks.

@stitesExpensify
Copy link
Contributor

I manually ran the script and it keeps failing unfortunately. Can you please create an openAI key and run the script yourself like it was described here?

@ShridharGoel
Copy link
Contributor Author

@parasharrajat The other translations are added now.

Copy link
Member

@parasharrajat parasharrajat left a comment

Choose a reason for hiding this comment

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

@ShridharGoel It is all messed up. Can you carefully check all translation files and sync them.

  1. Same key structure.
  2. same key location.
  3. All translation files have same changes except strings. in different languages.

@ShridharGoel
Copy link
Contributor Author

@parasharrajat Updated the order of strings.

Copy link
Member

@parasharrajat parasharrajat left a comment

Choose a reason for hiding this comment

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

May be you are not seeing what I am seeing but there are still issues.

Comment on lines -1037 to -1040
dragReceiptBeforeEmail: 'Drag a receipt onto this page, forward a receipt to ',
dragReceiptsBeforeEmail: 'Drag receipts onto this page, forward receipts to ',
dragReceiptAfterEmail: ' or choose a file to upload below.',
dragReceiptsAfterEmail: ' or choose files to upload below.',
Copy link
Member

Choose a reason for hiding this comment

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

This change is not consistent.

@parasharrajat
Copy link
Member

Also, attach recordings of the flow impacted on all platforms.

Copy link
Member

@parasharrajat parasharrajat left a comment

Choose a reason for hiding this comment

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

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 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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.js 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 form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label 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.
  • 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.

🎀 👀 🎀 C+ reviewed

@melvin-bot melvin-bot bot requested a review from inimaga October 7, 2025 08:48
@inimaga inimaga merged commit 3f19f38 into Expensify:main Oct 7, 2025
20 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Oct 7, 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.

@roryabraham
Copy link
Contributor

@shawnborton @trjExpensify for future reference, you can run translations on any given PR by triggering this workflow: https://github.com/Expensify/App/actions/workflows/generateTranslations.yml

image

@roryabraham
Copy link
Contributor

@shawnborton
Copy link
Contributor

Oh, great to know!

@OSBotify
Copy link
Contributor

OSBotify commented Oct 8, 2025

🚀 Deployed to staging by https://github.com/inimaga in version: 9.2.27-0 🚀

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

@IuliiaHerets
Copy link

Hi @ShridharGoel , the new upload receipts UI on the scan tab is seen on Web & desktop only. No changes on mweb, iOS & Android apps. Is it expected, or do we need to log an issue?
IMG_0918

@ShridharGoel
Copy link
Contributor Author

That's expected

@OSBotify
Copy link
Contributor

OSBotify commented Oct 8, 2025

🚀 Deployed to production by https://github.com/lakchote in version: 9.2.27-6 🚀

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.