[CP Staging] Fix `Share it with my accountant` navigation flow by VickyStash · Pull Request #62364 · Expensify/App

VickyStash · 2025-05-20T11:43:48Z

Explanation of Change

Fix Share it with my accountant navigation flow

Fixed Issues

$ #62359
$ #62365

Tests

Verify that no errors appear in the JS console

Go to self DM.
Submit a track expense in self DM.
Click Share it with my accountant.
Enter email and select user.
Click New workspace.
Make sure you navigated to the confirmation page, same way as it works on production now.

Offline tests

Same, as in the Tests section.

QA Steps

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

Verify that no errors appear in the JS console

Same, as in the Tests section.

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

MacOS: Chrome / Safari

web.mp4

VickyStash · 2025-05-20T12:02:37Z

Jest test is failing on other PRs as well (https://github.com/Expensify/App/actions/runs/15136763667/job/42550261953, https://github.com/Expensify/App/actions/runs/15136611567/job/42549758474), so it's not caused by this PR.

melvin-bot · 2025-05-20T12:02:48Z

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

dukenv0307 · 2025-05-20T13:13:45Z

@VickyStash We got 1 failed test

dukenv0307 · 2025-05-20T13:15:35Z

Screen.Recording.2025-05-20.at.20.12.42.mov

I can't create expense on native platform

dukenv0307 · 2025-05-20T13:16:25Z

But it already navigated to confirm page

dukenv0307 · 2025-05-20T13:16:51Z

Can you please take a look? @VickyStash

…h-accountant

VickyStash · 2025-05-20T13:54:57Z

@dukenv0307 I was able to reproduce the issue you reported, but I need to step out for ~2h, I'll try to fix it right after I'm back

carlosmiceli · 2025-05-20T16:06:17Z

Any chance this PR also fixes #62365? Just now starting to look into it cc @cristipaval @VickyStash

VickyStash · 2025-05-20T16:08:37Z

Any chance this PR also fixes #62365? Just now starting to look into it cc @cristipaval @VickyStash

@carlosmiceli This issue looks exactly what @dukenv0307 reported in this comment. I'm preparing a fix, will push it to this PR soon!

carlosmiceli · 2025-05-20T16:18:48Z

This issue looks exactly what @dukenv0307 reported in this comment. I'm preparing a fix, will push it to this PR soon!

Niceeeee, thanks Vicky! Keep me posted 🫶

VickyStash · 2025-05-20T16:50:21Z

@dukenv0307 I've pushed a fix for this issue, could you please check it? It seems to be the same as #62365

ex.mp4

VickyStash · 2025-05-20T17:03:23Z

Note: the lint is failing due to a known issue, it will be handled in #61910

src/pages/iou/request/step/IOURequestStepParticipants.tsx

dukenv0307 · 2025-05-20T17:35:55Z

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

Screen.Recording.2025-05-21.at.00.15.39.mov

Android: mWeb Chrome

Screen.Recording.2025-05-21.at.00.14.42.mov

iOS: HybridApp

Screen.Recording.2025-05-21.at.00.19.17.mov

iOS: mWeb Safari

Screen.Recording.2025-05-21.at.00.14.09.mov

MacOS: Chrome / Safari

Screen.Recording.2025-05-21.at.00.11.59.mov

MacOS: Desktop

Screen.Recording.2025-05-21.at.00.18.49.mov

OSBotify · 2025-05-20T17:58:50Z

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

…2359-share-with-accountant Fix `Share it with my accountant` navigation flow (cherry picked from commit 81a040d) (cherry-picked to staging by arosiclair)

github-actions · 2025-05-20T18:50:25Z

🚀 Cherry-picked to staging by https://github.com/arosiclair in version: 9.1.47-2 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

github-actions · 2025-05-21T18:08:48Z

🚀 Deployed to production by https://github.com/arosiclair in version: 9.1.47-6 🚀

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

github-actions · 2025-05-21T19:11:14Z

🚀 Deployed to production by https://github.com/arosiclair in version: 9.1.47-6 🚀

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

github-actions · 2025-05-21T19:47:20Z

🚀 Deployed to production by https://github.com/arosiclair in version: 9.1.47-6 🚀

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

truph01 · 2025-09-28T10:35:15Z

src/pages/iou/request/step/IOURequestStepParticipants.tsx

-                iouType={iouType}
-                action={action}
-            />
+            {transactions.length > 0 && (


Ah, I got the reason. Please ignore my comment above.

VickyStash added 2 commits May 20, 2025 13:39

Fix navigation logic

f886ea3

Re-run tests

4fb9b39

VickyStash marked this pull request as ready for review May 20, 2025 12:02

VickyStash requested a review from a team as a code owner May 20, 2025 12:02

melvin-bot bot requested review from allroundexperts and removed request for a team May 20, 2025 12:02

VickyStash mentioned this pull request May 20, 2025

[Due for payment 2025-05-30] [Due for payment 2025-05-28] Track expense - After selecting a category, app returns to Share list instead of Confirm page #62359

Closed

8 tasks

cristipaval requested review from dukenv0307 and removed request for allroundexperts May 20, 2025 12:40

Merge branch 'refs/heads/main' into VickyStash/bugfix/62359-share-wit…

c9fe36f

…h-accountant

carlosmiceli mentioned this pull request May 20, 2025

[Due for payment 2025-05-30] [Due for payment 2025-05-28] [$250] Android - Expense - Unable to submit track expense to a workspace. #62365

Closed

8 tasks

Fix expense creation on android

47a3017

dukenv0307 reviewed May 20, 2025

View reviewed changes

src/pages/iou/request/step/IOURequestStepParticipants.tsx Outdated Show resolved Hide resolved

Minor improvement

c4f809d

dukenv0307 approved these changes May 20, 2025

View reviewed changes

melvin-bot bot requested a review from carlosmiceli May 20, 2025 17:36

carlosmiceli approved these changes May 20, 2025

View reviewed changes

cristipaval approved these changes May 20, 2025

View reviewed changes

carlosmiceli merged commit 81a040d into Expensify:main May 20, 2025
18 of 19 checks passed

OSBotify added the CP Staging marks PRs that have been CP'd to staging label May 20, 2025

github-actions bot mentioned this pull request May 20, 2025

Deploy Checklist: New Expensify 2025-05-20 #62353

Closed

90 tasks

arosiclair changed the title ~~Fix Share it with my accountant navigation flow~~ [CP Staging] Fix Share it with my accountant navigation flow May 20, 2025

truph01 reviewed Sep 28, 2025

View reviewed changes

truph01 mentioned this pull request Sep 28, 2025

perf: Improve performance of selecting participants #70860

Merged

51 tasks

Conversation

VickyStash commented May 20, 2025 • edited by arosiclair Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

VickyStash commented May 20, 2025

Uh oh!

melvin-bot bot commented May 20, 2025

Uh oh!

dukenv0307 commented May 20, 2025

Uh oh!

dukenv0307 commented May 20, 2025

Uh oh!

dukenv0307 commented May 20, 2025

Uh oh!

dukenv0307 commented May 20, 2025

Uh oh!

VickyStash commented May 20, 2025

Uh oh!

carlosmiceli commented May 20, 2025

Uh oh!

VickyStash commented May 20, 2025

Uh oh!

carlosmiceli commented May 20, 2025

Uh oh!

VickyStash commented May 20, 2025

Uh oh!

VickyStash commented May 20, 2025

Uh oh!

Uh oh!

dukenv0307 commented May 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

OSBotify commented May 20, 2025

Uh oh!

github-actions bot commented May 20, 2025

Uh oh!

github-actions bot commented May 21, 2025

Uh oh!

github-actions bot commented May 21, 2025

Uh oh!

github-actions bot commented May 21, 2025

Uh oh!

This comment was marked as outdated.

Uh oh!

truph01 Sep 28, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

VickyStash commented May 20, 2025 •

edited by arosiclair

Loading

dukenv0307 commented May 20, 2025 •

edited

Loading