fix: prevent crash due to empty report #47997

dominictb · 2024-08-26T12:35:26Z

Details

Fixed Issues

$ #46980
PROPOSAL: #46980 (comment)

Tests

Paste this url to any chat https://dev.new.expensify.com:8082/r/undefined.
Click on the above url message.
Submit 2 expenses to any workspace.
Click on the report preview in step 3.
Delete the first expense

Verify app is not crash

Verify that no errors appear in the JS console

Offline tests

QA Steps

Paste this url to any chat https://staging.new.expensify.com/r/undefined.
Click on the above url message.
Submit 2 expenses to any workspace.
Click on the report preview in step 3.
Delete the first expense

Verify app is not crash

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

compressed_android.webm.mp4

Android: mWeb Chrome

compressed_aweb.webm.mp4

iOS: Native

compressed_ios.mp4.mp4

iOS: mWeb Safari

compressed_iweb.mp4.mp4

MacOS: Chrome / Safari

compressed_web.mov.mp4

MacOS: Desktop

compressed_web.mov.mp4

melvin-bot · 2024-08-26T12:35:31Z

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

mollfpr · 2024-08-27T19:05:02Z

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

47997.Android.mp4

Android: mWeb Chrome

47997.mWeb-Chrome.mp4

iOS: Native

47997.iOS.mov

iOS: mWeb Safari

47997.mWeb-Safari.mov

MacOS: Chrome / Safari

47997.Web.mp4

MacOS: Desktop

47997.Desktop.mp4

mollfpr · 2024-08-28T16:26:27Z

src/pages/home/report/ReportActionItemContentCreated.tsx

@@ -149,7 +149,7 @@ function ReportActionItemContentCreated({contextValue, parentReportAction, trans
    if (ReportUtils.isExpenseReport(report) || ReportUtils.isIOUReport(report) || ReportUtils.isInvoiceReport(report)) {
        return (
            <OfflineWithFeedback pendingAction={action.pendingAction}>
-                {transactionThreadReport && !isEmptyObject(transactionThreadReport) ? (
+                {!isEmptyObject(transactionThreadReport?.reportID) ? (


It doesn't make sense to me we using isEmptyObject to check a string.

@mollfpr

App/src/pages/iou/request/IOURequestStartPage.tsx

Line 60 in b9af3d1

const isFromGlobalCreate = isEmptyObject(report?.reportID);

we are using this pattern to check if a report is a valid report.

mollfpr · 2024-08-29T18:34:20Z

@dominictb I think iOS is still showing the crash. Also, the result on a small screen briefly shows the not found page after deleting the expense.

iOS

Simulator.Screen.Recording.-.iPhone.15.Pro.17.2.-.2024-08-30.at.01.15.17.mov

mWeb - Safari

Simulator.Screen.Recording.-.iPhone.15.Pro.17.2.-.2024-08-30.at.01.24.08.mov

dominictb · 2024-08-30T02:36:30Z

@mollfpr I have merged main

iOS mWeb: No more not found page

Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2024-08-30.at.09.29.03.mp4

iOS: I couldn't get the crash anymore, but even the crash shown in the previous video doesn't seem to relate to my fix.

Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2024-08-30.at.09.32.06.mp4

mollfpr

LGTM!

The issue not found page shown briefly on the small screen still reproducible, but this is also happen on staging.

OSBotify · 2024-09-17T01:09:33Z

✋ 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 · 2024-09-17T20:51:24Z

🚀 Deployed to staging by https://github.com/aldo-expensify in version: 9.0.37-0 🚀

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

OSBotify · 2024-09-19T23:32:59Z

🚀 Deployed to production by https://github.com/grgia in version: 9.0.38-4 🚀

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

fix: prevent crash due to empty report

80a8f35

dominictb requested a review from a team as a code owner August 26, 2024 12:35

melvin-bot bot requested review from mollfpr and removed request for a team August 26, 2024 12:35

mollfpr reviewed Aug 28, 2024

View reviewed changes

Merge remote-tracking branch 'origin/main' into fix/46980-distance-req

f97ad25

mollfpr approved these changes Sep 2, 2024

View reviewed changes

melvin-bot bot requested a review from aldo-expensify September 2, 2024 08:28

aldo-expensify approved these changes Sep 17, 2024

View reviewed changes

aldo-expensify merged commit bc29cad into Expensify:main Sep 17, 2024
16 checks passed

github-actions bot mentioned this pull request Sep 17, 2024

Deploy Checklist: New Expensify 2024-09-17 #49356

Closed

40 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: prevent crash due to empty report #47997

fix: prevent crash due to empty report #47997

dominictb commented Aug 26, 2024 •

edited

Loading

melvin-bot bot commented Aug 26, 2024

mollfpr commented Aug 27, 2024 •

edited

Loading

mollfpr Aug 28, 2024

dominictb Aug 29, 2024

mollfpr commented Aug 29, 2024

dominictb commented Aug 30, 2024

mollfpr left a comment

OSBotify commented Sep 17, 2024

OSBotify commented Sep 17, 2024

OSBotify commented Sep 19, 2024

fix: prevent crash due to empty report #47997

fix: prevent crash due to empty report #47997

Conversation

dominictb commented Aug 26, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Aug 26, 2024

mollfpr commented Aug 27, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

mollfpr Aug 28, 2024

Choose a reason for hiding this comment

dominictb Aug 29, 2024

Choose a reason for hiding this comment

mollfpr commented Aug 29, 2024

dominictb commented Aug 30, 2024

mollfpr left a comment

Choose a reason for hiding this comment

OSBotify commented Sep 17, 2024

OSBotify commented Sep 17, 2024

OSBotify commented Sep 19, 2024

dominictb commented Aug 26, 2024 •

edited

Loading

mollfpr commented Aug 27, 2024 •

edited

Loading