fix: User avatar and email does not show when using Submit

[nkdengineer]

Details

Fixed Issues

$ #44295
PROPOSAL: #44295 (comment)

Tests

1. Global Create > Track Expense
2. Input the amount, description > Track
3. This will take you to your DM
4. Select Submit it to someone in the actionable whispers
5. Input the new user email
6. Submit it to them
7. Verify that: The avatar and email of the user you've submitted an expense to shows in the new transaction comment

• Verify that no errors appear in the JS console

Offline tests

QA Steps

1. Global Create > Track Expense
2. Input the amount, description > Track
3. This will take you to your DM
4. Select Submit it to someone in the actionable whispers
5. Input the new user email
6. Submit it to them
7. Verify that: The avatar and email of the user you've submitted an expense to shows in the new transaction comment

• 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 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
    • If any non-english text was added/modified, I verified the translation was requested/reviewed 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.js 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.
• 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: mWeb Chrome

android-mweb.mov

iOS: Native

iOS: mWeb Safari

ios-mweb.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

[melvin-bot]

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

[shubham1206agra]

Screen.Recording.2024-07-25.at.10.09.30.AM.mov

@nkdengineer Your solution is not working correctly here.

[shubham1206agra]

Sent the response of API in DM.

[nkdengineer]

@shubham1206agra I'm still working fine, please check again

ios-mweb.mov

[shubham1206agra]

Still happening to me.

[shubham1206agra]

@nkdengineer Bump on this.

[nkdengineer]

@shubham1206agra please add more detailed steps and video so that I can follow your issue

[shubham1206agra]

Just do the original steps

[nkdengineer]

@shubham1206agra maybe the problem happens when in strict mode, you can turn it off here

[shubham1206agra]

@nkdengineer Already disabled. The problem is still occurring.

[shubham1206agra]

@nkdengineer Bump here.

[nkdengineer]

@shubham1206agra I can reproduce it now, I will investigate and update tomorrow.

[nkdengineer]

@shubham1206agra I missed checking out this branch yesterday then I can reproduce this bug. I tried many times again but can't reproduce now. Sorry for the confusion.

[shubham1206agra]

@nkdengineer Sorry, but at this stage. I can't approve this PR as it fixes nothing on my end.

[nkdengineer]

@grgia Can you please add a build here? I need to re-test in the real device to confirm this bug still happens or not.

[nkdengineer]

@shubham1206agra Let's wait for a build here and we can re-test again if it still happens.

[grgia]

Triggered a test build @nkdengineer !

[nkdengineer]

@grgia Unfortunately, the build is failing on all platforms.

[grgia]

@nkdengineer it triggered two builds by accident and I cancelled the first, second is still building!

[nkdengineer]

Thanks.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/45393/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/45393/index.html
Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/45393/NewExpensify.dmg	https://45393.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[nkdengineer]

@shubham1206agra Found the RCA when testing in the build web, ConvertTrackedExpenseToRequest API BE returns only the personal details of the current user, and the participant also only has the current user. If we open another report and go back, OpenReport API is called and then the necessary is returned.

The offline mode works well.

I'm not sure why I can't reproduce locally on my side. Maybe on my side OpenReport API is called immediately after ConvertTrackedExpenseToRequest is called.

[shubham1206agra]

@grgia Is it possible for you to look into BE why this is happening?

[grgia]

@shubham1206agra @nkdengineer

API BE returns only the personal details of the current user, and the participant also only has the current user.

Could you remind me the expected behavior here

[nkdengineer]

@grgia the expected behavior here is. For ConvertTrackedExpenseToRequest API, BE should

1. personalDetailsList, return the personal details of the user that is payerEmail in the param of the API

2. report (invoice report), return the correct participants that contain the payerEmail user. Current this API returns participant only has the current user

[grgia]

@nkdengineer @shubham1206agra Let me take a look at the BE this afternoon, please let me know if there are any specific steps I need to consider

[grgia]

I also see the call to OpenReport after in Dev @nkdengineer but not in the adhoc test as well

[grgia]

Either way I can update ConvertTrackedExpenseToRequest to send both participants, I have a PR up here (internal repo)

[nkdengineer]

@grgia Got it. We should return the data correctly as I mentioned here #45393 (comment) to prevent loading show in header before OpenReport API is complete or it's not called.

[grgia]

I verified locally that the linked PR will send the necessary detail. It's in review now and I'll keep you updated

[muttmuure]

@nkdengineer are you unblocked now? The linked Auth PR is on production

[nkdengineer]

@muttmuure Thanks for your update, let me test again.

[nkdengineer]

@shubham1206agra I tested in the ad-hoc build again and the bug is fixed after the BE changes. Can you please double-check with your local again, thanks.

[shubham1206agra]

@nkdengineer Can you merge main here?

[nkdengineer]

@shubham1206agra Merged main.

[shubham1206agra]

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

Android: mWeb Chrome

Screen.Recording.2024-08-05.at.5.53.37.PM.mov

iOS: Native

Screen.Recording.2024-08-05.at.6.07.47.PM.mov

iOS: mWeb Safari

Screen.Recording.2024-08-05.at.5.43.39.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-08-05.at.5.40.17.PM.mov

MacOS: Desktop

Screen.Recording.2024-08-05.at.5.58.06.PM.mov

[OSBotify]

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

🚀 Deployed to staging by https://github.com/grgia in version: 9.0.18-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.18-10 🚀

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