fix: Payer section goes missing from payed money request preview #60168

nkdengineer · 2025-04-14T04:15:05Z

Explanation of Change

Fixed Issues

$ #59688
PROPOSAL: #59688 (comment)

Tests

Do a manual request from userA to userB
Make userB mark the request as paid elsewhere
The request from userA's perspective should look like the screenshot (there is a section userA -> userB )
Log out userA and log back in
Go to the money request preview
Verify that: Requester -> Payer section displayed after user login

Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android.mov

Android: mWeb Chrome

android-mweb.mov

iOS: Native

ios.mov

iOS: mWeb Safari

ios-mweb.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

melvin-bot · 2025-04-14T16:12:06Z

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

dominictb · 2025-04-15T19:15:58Z

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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2025-04-16.at.02.26.33.mov

MacOS: Desktop

Screen.Recording.2025-04-16.at.02.29.08.mov

dominictb · 2025-04-15T19:37:25Z

@nkdengineer When I log back in, the last message in LHN for user B is not the IOU:

Can you check?

nkdengineer · 2025-04-16T18:23:51Z

@nkdengineer When I log back in, the last message in LHN for user B is not the IOU:

@dominictb i can't reproduce this bug

dominictb · 2025-04-16T23:08:13Z

@nkdengineer Steps:

A sends a message to B
A submits an IOU to B
B pays the IOU
A switches to another report (The key is not to trigger OpenReport)
A goes to Troubleshoot > Reset cache
A goes back to LHN (do not open the DM with B)
Observe the last message in LHN for the DM

Actual result: It shows the first message in the DM
Expected result: It shows paid ${amount}

nkdengineer · 2025-04-21T02:48:38Z

checking now

nkdengineer · 2025-04-21T03:19:38Z

@nkdengineer When I log back in, the last message in LHN for user B is not the IOU:

@dominictb We don't have transaction data until we open DM report => no data to show last message in LHN

Screen.Recording.2025-04-21.at.10.18.08.mov

dominictb · 2025-04-21T07:01:32Z

@nkdengineer Lint.

dominictb · 2025-04-21T07:18:37Z

@nkdengineer

We don't have transaction data until we open DM report => no data to show last message in LHN

Is this purely BE or is there anything we can fix in FE?

nkdengineer · 2025-04-21T08:07:21Z

Is this purely BE or is there anything we can fix in FE?

this is purely BE

nkdengineer · 2025-04-21T08:25:29Z

@dominictb i fixed

dominictb

Except for the LHN's last message bug mentioned here reproduced by these steps. The root cause is that the BE does not return the full report and reportActions data for that report, it only returns the first report action. It's out of scope and should be handled separately.

PR looks good

rlinoz

Thanks!

OSBotify · 2025-04-21T13:05:47Z

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

github-actions · 2025-04-21T23:40:55Z

🚀 Deployed to staging by https://github.com/rlinoz in version: 9.1.31-0 🚀

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

shawnborton · 2025-04-22T13:55:57Z

@nkdengineer did this PR cause this regression here? #60647

nkdengineer · 2025-04-22T13:59:31Z

@shawnborton I'm pretty sure this come from #59806 that reverse the correct logic

shawnborton · 2025-04-22T14:01:23Z

Hmm we only started noticing this today. Not only that, the From/To now seems to be reversed. In this case here, I actually sent the expense to Yuwen, but now it says that Yuwen sent the expense to me:

github-actions · 2025-04-23T18:17:26Z

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.1.31-3 🚀

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

nkdengineer added 2 commits April 14, 2025 11:14

fix: Payer section goes missing from payed money request preview

c0161a6

fix lint

d597603

nkdengineer marked this pull request as ready for review April 14, 2025 16:12

nkdengineer requested a review from a team as a code owner April 14, 2025 16:12

melvin-bot bot requested review from dominictb and removed request for a team April 14, 2025 16:12

Merge branch 'main' into fix/59688

2e46052

nkdengineer added 3 commits April 21, 2025 10:04

resolve conflict

105f62b

fix lint

d7b95c1

fix prettier

379d704

fix lint

f1f36c1

remove useless code

86dc46f

dominictb approved these changes Apr 21, 2025

View reviewed changes

melvin-bot bot requested a review from rlinoz April 21, 2025 10:27

rlinoz approved these changes Apr 21, 2025

View reviewed changes

rlinoz merged commit fc9d478 into Expensify:main Apr 21, 2025
17 checks passed

github-actions bot mentioned this pull request Apr 21, 2025

Deploy Checklist: New Expensify 2025-04-21 #60596

Closed

31 tasks

jponikarchuk mentioned this pull request Apr 22, 2025

[$250] Expense - The expense preview shows Payer → Requester instead of Requester → Payer. #60607

Closed

8 tasks

mountiny mentioned this pull request Apr 22, 2025

[Better Expense Report View] Expense preview card on expense report preview incorrectly shows From/To header #60647

Closed

melvin-bot bot mentioned this pull request Apr 23, 2025

[Due for payment 2025-04-30] [$250] DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in #59688

Closed

18 tasks

fix: Payer section goes missing from payed money request preview #60168

fix: Payer section goes missing from payed money request preview #60168

Uh oh!

Conversation

nkdengineer commented Apr 14, 2025 • edited 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!

melvin-bot bot commented Apr 14, 2025

Uh oh!

dominictb commented Apr 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

dominictb commented Apr 15, 2025

Uh oh!

nkdengineer commented Apr 16, 2025

Uh oh!

dominictb commented Apr 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nkdengineer commented Apr 21, 2025

Uh oh!

nkdengineer commented Apr 21, 2025

Uh oh!

dominictb commented Apr 21, 2025

Uh oh!

dominictb commented Apr 21, 2025

Uh oh!

nkdengineer commented Apr 21, 2025

Uh oh!

nkdengineer commented Apr 21, 2025

Uh oh!

dominictb left a comment

Choose a reason for hiding this comment

Uh oh!

rlinoz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Apr 21, 2025

Uh oh!

github-actions bot commented Apr 21, 2025

Uh oh!

shawnborton commented Apr 22, 2025

Uh oh!

nkdengineer commented Apr 22, 2025

Uh oh!

shawnborton commented Apr 22, 2025

Uh oh!

github-actions bot commented Apr 23, 2025

Uh oh!

Uh oh!

nkdengineer commented Apr 14, 2025 •

edited

Loading

dominictb commented Apr 15, 2025 •

edited

Loading

dominictb commented Apr 16, 2025 •

edited

Loading