Skip to content

Manual expense flow UI refactor r1#83695

Merged
puneetlath merged 30 commits intoExpensify:mainfrom
ChavdaSachin:ManualExpense-flow-UI-refactor-r1
Mar 24, 2026
Merged

Manual expense flow UI refactor r1#83695
puneetlath merged 30 commits intoExpensify:mainfrom
ChavdaSachin:ManualExpense-flow-UI-refactor-r1

Conversation

@ChavdaSachin
Copy link
Copy Markdown
Contributor

@ChavdaSachin ChavdaSachin commented Feb 27, 2026

Explanation of Change

Fixed Issues

$ #82586
PROPOSAL:

Tests

Same as QA.

  • Verify that no errors appear in the JS console

Offline tests

Same as QA.

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Test using Expensifail account.

  1. Open the App.
  2. Clock FAB -> Manual.
  3. Complete the steps to reach the confirmation page.
  4. Verify confirmation page has inline text input for the field Amount.
  5. Verify amount is editable.
  6. Verify currency select button and the currency picker are working as expected.
  7. Clear the amount value and click create expense, Verify Field required error is visible.
  8. On small screens: Verify sign flip button is visible and working as expected.
  9. Enter an amount value and click create expense, Verify IOU created is of correct value.
  10. Repeat Step 3-9 for Track Distance -> Map /Manual/Odometer
  • 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 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
Screen.Recording.2026-03-16.at.5.30.47.PM.mov
Android: mWeb Chrome
iOS: Native

Uploading Screen Recording 2026-03-16 at 5.37.10 PM.mov…

iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-03-16.at.5.23.27.PM.mov

@ChavdaSachin ChavdaSachin marked this pull request as ready for review March 9, 2026 04:23
@ChavdaSachin ChavdaSachin requested review from a team as code owners March 9, 2026 04:23
@melvin-bot melvin-bot bot requested review from JmillsExpensify and ShridharGoel and removed request for a team March 9, 2026 04:23
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Mar 9, 2026

@ShridharGoel 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 the request for review from a team March 9, 2026 04:23
@ChavdaSachin
Copy link
Copy Markdown
Contributor Author

ChavdaSachin commented Mar 9, 2026

Could someone please trigger an ad-hoc build and request applause for testing?

This PR implemented inline input for IOU field - Amount, on IOU confirmation page.

cc. @JmillsExpensify @puneetlath

@ChavdaSachin
Copy link
Copy Markdown
Contributor Author

ps. I'd recommit everything with meaningful messages once the component is confirmed to be working as expected.

@trjExpensify
Copy link
Copy Markdown
Contributor

@ChavdaSachin can you fix that conflict?

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 9, 2026

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

@github-actions

This comment has been minimized.

@ChavdaSachin
Copy link
Copy Markdown
Contributor Author

Applause was asked to test this PR right?

@ShridharGoel
Copy link
Copy Markdown
Contributor

Screen.Recording.2026-03-10.at.11.44.53.PM.mov

@ShridharGoel
Copy link
Copy Markdown
Contributor

@ChavdaSachin Can you add the description and testing steps and also mention that this only handles the amount field?

@ChavdaSachin
Copy link
Copy Markdown
Contributor Author

@ChavdaSachin Can you add the description and testing steps and also mention that this only handles the amount field?

Sure.

@ShridharGoel for the recording video you posted, is there any bug you want to highlight?
As I see it working as expected.

@ShridharGoel
Copy link
Copy Markdown
Contributor

for the recording video you posted, is there any bug you want to highlight?

No, it was just for showing the flow so that others can have a look since screenshots/videos were not there in the description.

@puneetlath
Copy link
Copy Markdown
Contributor

Applause was asked to test this PR right?

Not that I'm aware of. Given that this is behind a beta, can we ask them to test on staging? Or do you think there's some risk in spite of the beta?

@JmillsExpensify
Copy link
Copy Markdown
Contributor

How do I get on the beta for this PR?

@ChavdaSachin
Copy link
Copy Markdown
Contributor Author

@JmillsExpensify you could run following command in console

Onyx.merge('betas', ['newManualExpenseFlow']);

To open console: press f12 button in browser, and find the console tab from the navbar of newly opened browser tools section

@ChavdaSachin
Copy link
Copy Markdown
Contributor Author

Not that I'm aware of. Given that this is behind a beta, can we ask them to test on staging? Or do you think there's some risk in spite of the beta?

Then please ask them to test, as this PR would tough some core functions as well, which may have side effects.

And just to make sure - @puneetlath the expensifail accounts by default have beta key 'all' added right?

@JmillsExpensify
Copy link
Copy Markdown
Contributor

Thanks! It's not working for me though.

CleanShot 2026-03-12 at 00 23 31@2x

@ShridharGoel
Copy link
Copy Markdown
Contributor

Thanks! It's not working for me though.

Are you doing it on 83695.pr-testing.expensify.com ?

@ChavdaSachin
Copy link
Copy Markdown
Contributor Author

Changes are up, ready for review.

cc. @ShridharGoel @puneetlath

@puneetlath
Copy link
Copy Markdown
Contributor

@ShridharGoel can you please prioritize another round of review today?

@ShridharGoel
Copy link
Copy Markdown
Contributor

Bug: Expense can be created without any amount instead of showing an error, after the amount is cleared in the inline field. This is because the draft amount is not cleared in handleAmountChange().

Screen.Recording.2026-03-23.at.10.50.47.PM.mov

@ChavdaSachin
Copy link
Copy Markdown
Contributor Author

ChavdaSachin commented Mar 23, 2026

@ShridharGoel good catch, this bug would be handled in the final PR, if I would patch it up now it's highly likely we might not need those changes during final phase and end up reverting.

@melvin-bot melvin-bot bot requested a review from puneetlath March 23, 2026 21:23
@ShridharGoel
Copy link
Copy Markdown
Contributor

Would it be good to add "NoQA" here and get it tested once the whole feature is done?

@puneetlath
Copy link
Copy Markdown
Contributor

Yes, I think that makes sense.

Copy link
Copy Markdown
Contributor

@puneetlath puneetlath left a comment

Choose a reason for hiding this comment

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

Two super minor comments. Can we address and merge today?

@ChavdaSachin
Copy link
Copy Markdown
Contributor Author

@puneetlath I did not add the GH comment link to the code. As To Do list on the parent issue should be self sufficient for the future references.

Ready to merge.

@puneetlath puneetlath merged commit b05f115 into Expensify:main Mar 24, 2026
39 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

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

@OSBotify
Copy link
Copy Markdown
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
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.3.44-0 🚀

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

Bundle Size Analysis (Sentry):

@nlemma
Copy link
Copy Markdown

nlemma commented Mar 25, 2026

Deploy Blocker #86342 was identified to be related to this PR.

@jponikarchuk
Copy link
Copy Markdown

Deploy Blocker #86343 was identified to be related to this PR.

@jponikarchuk
Copy link
Copy Markdown

This PR failing because of the issue #86343
This issue is reproducible in: Web

wildan-m added a commit to wildan-m/App that referenced this pull request Mar 25, 2026
PR Expensify#83695 added isNewManualExpenseFlowEnabled guards that suppressed
the amount from the Create/Track button text, but the Split button
was not modified — causing an inconsistency where Split shows the
amount but Create does not.

Remove the isNewManualExpenseFlowEnabled conditions from the button
text logic so the Create button always shows the amount (e.g.
"Create $500.00 expense") regardless of the flow, consistent with
the Split button behavior.

Fixes Expensify#86342
@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.3.47-0 🚀

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

Bundle Size Analysis (Sentry):

@jponikarchuk
Copy link
Copy Markdown

Deploy Blocker #86394 was identified to be related to this PR.

@ShridharGoel
Copy link
Copy Markdown
Contributor

We didn't add NoQA here? #83695 (comment)

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.3.48-2 🚀

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.

9 participants