[CP Staging] fix: Blank page after returning to IOU report from thread and deleting the other request #40157

tienifr · 2024-04-12T03:12:15Z

Details

Fixed Issues

$ #40087
PROPOSAL: #40087 (comment)

Tests

Go to staging.new.expensify.com
Go to any chat.
Create two IOUs.
Go to the transaction thread of the first IOU.
Click on the header subtitle to return to IOU report.
Right click on the second IOU preview > Delete request.
Delete the request.
App will open one report transaction view (combined IOU report).

Verify that no errors appear in the JS console

Offline tests

QA Steps

Go to staging.new.expensify.com
Go to any chat.
Create two IOUs.
Go to the transaction thread of the first IOU.
Click on the header subtitle to return to IOU report.
Right click on the second IOU preview > Delete request.
Delete the request.
App will open one report transaction view (combined IOU report).

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

web-resize.mp4

Android: mWeb Chrome

web-resize.mp4

iOS: Native

web-resize.mp4

iOS: mWeb Safari

web-resize.mp4

MacOS: Chrome / Safari

web-resize.mp4

MacOS: Desktop

web-resize.mp4

…g the other request

melvin-bot · 2024-04-12T03:27:48Z

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

youssef-lr · 2024-04-12T15:05:05Z

Friendly bump @rushatgabhane

rushatgabhane · 2024-04-12T18:19:07Z

ETA 2 hours

rushatgabhane · 2024-04-12T20:47:09Z

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-04-13.at.03.02.48.mov

iOS: Native

Screen.Recording.2024-04-13.at.02.53.34.mov

iOS: mWeb Safari

Screen.Recording.2024-04-13.at.02.56.29.mov

MacOS: Chrome / Safari

Screen.Recording.2024-04-13.at.02.52.05.mov

MacOS: Desktop

Screen.Recording.2024-04-13.at.02.58.56.mov

youssef-lr

LGTM!

OSBotify · 2024-04-13T00:49:18Z

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

fix: Blank page after returning to IOU report from thread and deleting the other request (cherry picked from commit db9e01c)

OSBotify · 2024-04-15T15:18:12Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.4.62-7 🚀

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

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

OSBotify · 2024-04-18T04:34:45Z

🚀 Deployed to production by https://github.com/thienlnam in version: 1.4.62-17 🚀

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

hungvu193 · 2024-07-24T15:38:14Z

src/pages/home/ReportScreen.tsx

@@ -333,6 +333,14 @@ function ReportScreen({
    }

    const transactionThreadReportID = useMemo(() => ReportActionsUtils.getOneTransactionThreadReportID(report.reportID, reportActions ?? []), [report.reportID, reportActions]);
+
+    useEffect(() => {
+        if (!transactionThreadReportID || !route.params.reportActionID) {


We also need to add condition to check if the current report is one transaction thread too. Otherwise it will cause #44588. More details in this comment.

tienifr added 2 commits April 12, 2024 09:57

fix: Blank page after returning to IOU report from thread and deletin…

016df60

…g the other request

lint fix

fd337b9

tienifr marked this pull request as ready for review April 12, 2024 03:27

tienifr requested a review from a team as a code owner April 12, 2024 03:27

melvin-bot bot requested review from Ollyws and removed request for a team April 12, 2024 03:27

tienifr mentioned this pull request Apr 12, 2024

[HOLD for payment 2024-04-25] [$250] IOU - Blank page after returning to IOU report from thread and deleting the other request #40087

Closed

6 tasks

youssef-lr requested review from rushatgabhane and removed request for Ollyws April 12, 2024 15:04

rushatgabhane approved these changes Apr 12, 2024

View reviewed changes

melvin-bot bot requested a review from youssef-lr April 12, 2024 21:41

youssef-lr approved these changes Apr 13, 2024

View reviewed changes

youssef-lr merged commit db9e01c into Expensify:main Apr 13, 2024
16 checks passed

mountiny changed the title ~~fix: Blank page after returning to IOU report from thread and deleting the other request~~ [CP Staging] fix: Blank page after returning to IOU report from thread and deleting the other request Apr 15, 2024

OSBotify pushed a commit that referenced this pull request Apr 15, 2024

Merge pull request #40157 from tienifr/fix/40087

2f99466

fix: Blank page after returning to IOU report from thread and deleting the other request (cherry picked from commit db9e01c)

github-actions bot mentioned this pull request Apr 15, 2024

Deploy Checklist: New Expensify 2024-04-10 #40026

Closed

bernhardoj mentioned this pull request Jun 28, 2024

[HOLD for payment 2024-07-25] [$250] Pay someone - Paid system message is not highlighted when clicking on the message link #44588

Closed

6 tasks

hungvu193 reviewed Jul 24, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CP Staging] fix: Blank page after returning to IOU report from thread and deleting the other request #40157

[CP Staging] fix: Blank page after returning to IOU report from thread and deleting the other request #40157

tienifr commented Apr 12, 2024 •

edited

Loading

melvin-bot bot commented Apr 12, 2024

youssef-lr commented Apr 12, 2024

rushatgabhane commented Apr 12, 2024

rushatgabhane commented Apr 12, 2024 •

edited

Loading

youssef-lr left a comment

OSBotify commented Apr 13, 2024

OSBotify commented Apr 15, 2024

OSBotify commented Apr 18, 2024

hungvu193 Jul 24, 2024

[CP Staging] fix: Blank page after returning to IOU report from thread and deleting the other request #40157

[CP Staging] fix: Blank page after returning to IOU report from thread and deleting the other request #40157

Conversation

tienifr commented Apr 12, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Apr 12, 2024

youssef-lr commented Apr 12, 2024

rushatgabhane commented Apr 12, 2024

rushatgabhane commented Apr 12, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

youssef-lr left a comment

Choose a reason for hiding this comment

OSBotify commented Apr 13, 2024

OSBotify commented Apr 15, 2024

OSBotify commented Apr 18, 2024

hungvu193 Jul 24, 2024

Choose a reason for hiding this comment

tienifr commented Apr 12, 2024 •

edited

Loading

rushatgabhane commented Apr 12, 2024 •

edited

Loading