Fix crash on opening money request page after sign ing #23937

bernhardoj · 2023-07-31T16:50:59Z

Details

Opening/deep linking to money request page after sign in or for the first time crash the app.

Fixed Issues

$ #23420
PROPOSAL: #23420 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Sign out if you are signed in
Open staging.new.expensify.com/request/new*
Login
Verify the app does not crash

Use deep link for Android/iOS

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 / Chrome
- iOS / native
- iOS / 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- 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 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
- If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
- 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(themeColors.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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Screen.Recording.2023-07-31.at.23.47.08.mov

Mobile Web - Chrome

android.mweb.mov

Mobile Web - Safari

ios-mweb.mov

Desktop

deskto.mov

iOS

ios.mov

Android

android.mov

melvin-bot · 2023-07-31T16:51:04Z

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

bernhardoj · 2023-07-31T16:52:28Z

Currently, when you open the money request after signing in and press Next, the amount page will be shown again.

allroundexperts · 2023-07-31T18:34:44Z

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 / Chrome
- iOS / native
- iOS / 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- 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(themeColors.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 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

Web

Screen.Recording.2023-08-02.at.12.29.51.PM.mov

Mobile Web - Chrome

Screen.Recording.2023-08-02.at.12.55.09.PM.mov

Mobile Web - Safari

Screen.Recording.2023-08-02.at.12.53.08.PM.mov

Desktop

Screen.Recording.2023-08-02.at.12.33.02.PM.mov

iOS

Screen.Recording.2023-08-02.at.1.03.41.PM.mov

Android

Screen.Recording.2023-08-02.at.1.06.04.PM.mov

allroundexperts · 2023-07-31T19:34:35Z

Hi @bernhardoj!
I'm not fully sure about removing these default values altogether. This might cause a regression later on. I think a safer way would be to just add || CONST.CURRENCY.USD here.

Li357 · 2023-07-31T21:00:49Z

@bernhardoj Can we get this PR out ASAP? Currently listed as a deploy blocker and I'll cherry pick to staging once this is merged.

bernhardoj · 2023-08-01T03:42:53Z

@allroundexperts if we want to add || CONST.CURRENCY.USD, we also need to do that here

App/src/pages/iou/steps/MoneyRequestAmountPage.js

Lines 286 to 288 in cb8aac1

    
           useEffect(() => { 
        
               setSelectedCurrencyCode(props.iou.currency); 
        
           }, [props.iou.currency]);

The error and loading is never used. IOU Onyx is just a local onyx and is being used in the amount, participants, confirmation, description, and currency selection page. So it should be fine to remove it.

Using either || CONST.CURRENCY.USD or removing the IOU onyx initial value should work, but I still prefer the latter as we remove unnecessary code.

Also, if we keep the onyx initial value, then all of these default values will never be used

App/src/pages/iou/steps/MoneyRequestAmountPage.js

Lines 67 to 72 in cb8aac1

    
           iou: { 
        
               id: '', 
        
               amount: 0, 
        
               currency: CONST.CURRENCY.USD, 
        
               participants: [], 
        
           },

@Li357 I'm not sure why #23951 happens. Every time we click Split Bill or Request Money, we will set the currency here

App/src/libs/actions/IOU.js

Lines 64 to 72 in cb8aac1

    
           function resetMoneyRequestInfo(id = '') { 
        
               Onyx.merge(ONYXKEYS.IOU, { 
        
                   id, 
        
                   amount: 0, 
        
                   currency: lodashGet(currentUserPersonalDetails, 'localCurrencyCode', CONST.CURRENCY.USD), 
        
                   comment: '', 
        
                   participants: [], 
        
               }); 
        
           }

My guess is the Onyx merge is not completed yet (same root cause with #23937 (comment)), but I don't know why it happens on staging only. Maybe a recent Onyx update? (I see we have some issues that are caused by the recent Onyx update https://www.github.com/Expensify/App/issues/23962 https://www.github.com/Expensify/App/issues/23973)

Beamanator · 2023-08-01T08:47:07Z

FYI this Onyx PR was recently merged - https://github.com/Expensify/App/pull/23749/files

Just noting b/c there are some suspicions that a recent onyx change could have caused some issues

allroundexperts · 2023-08-01T19:37:02Z

@bernhardoj Can you please merge main?

allroundexperts · 2023-08-01T19:51:30Z

Also, do you know if there are any further steps to test this on native? I'm getting the following warning when opening the deep link without being logged in.

Screen.Recording.2023-08-02.at.12.49.49.AM.mov

bernhardoj · 2023-08-02T03:13:48Z

merged with main
@allroundexperts ah, yes you need to make sure the app is closed before opening the deep link. That's how I make it to work

allroundexperts

Looks good!

OSBotify · 2023-08-02T17:07: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.

OSBotify · 2023-08-03T17:42:01Z

🚀 Deployed to staging by https://github.com/madmax330 in version: 1.3.50-0 🚀

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

OSBotify · 2023-08-07T18:30:21Z

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.50-3 🚀

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

OSBotify · 2023-08-07T18:57:34Z

🚀 Deployed to staging by https://github.com/madmax330 in version: 1.3.51-0 🚀

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

OSBotify · 2023-08-09T08:46:42Z

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.51-2 🚀

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

remove unused initial onyx state

5827875

bernhardoj requested a review from a team as a code owner July 31, 2023 16:51

melvin-bot bot requested review from allroundexperts and removed request for a team July 31, 2023 16:51

Merge branch 'main' into fix/23420-money-request-crash

c5ef035

ahmedGaber93 mentioned this pull request Aug 1, 2023

request money open workspace details when selected workspace clicked. #23980

Merged

58 tasks

hannojg mentioned this pull request Aug 1, 2023

[HOLD for payment 2023-08-10] App crashes when clicking 'Split bill' button for newly created account #23951

Closed

6 tasks

Merge branch 'main' into fix/23420-money-request-crash

1501d7f

allroundexperts approved these changes Aug 2, 2023

View reviewed changes

melvin-bot bot requested a review from madmax330 August 2, 2023 08:12

madmax330 approved these changes Aug 2, 2023

View reviewed changes

madmax330 merged commit 1efc85f into Expensify:main Aug 2, 2023
12 checks passed

OSBotify mentioned this pull request Aug 3, 2023

Deploy Checklist: New Expensify 2023-08-03 #24121

Closed

86 tasks

OSBotify mentioned this pull request Aug 7, 2023

Deploy Checklist: New Expensify 2023-08-07 #24230

Closed

98 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix crash on opening money request page after sign ing #23937

Fix crash on opening money request page after sign ing #23937

bernhardoj commented Jul 31, 2023 •

edited

Loading

melvin-bot bot commented Jul 31, 2023

bernhardoj commented Jul 31, 2023

allroundexperts commented Jul 31, 2023 •

edited

Loading

allroundexperts commented Jul 31, 2023

Li357 commented Jul 31, 2023 •

edited

Loading

bernhardoj commented Aug 1, 2023 •

edited

Loading

Beamanator commented Aug 1, 2023

allroundexperts commented Aug 1, 2023

allroundexperts commented Aug 1, 2023

bernhardoj commented Aug 2, 2023

allroundexperts left a comment

OSBotify commented Aug 2, 2023

OSBotify commented Aug 3, 2023

OSBotify commented Aug 7, 2023

OSBotify commented Aug 7, 2023

OSBotify commented Aug 9, 2023

Fix crash on opening money request page after sign ing #23937

Fix crash on opening money request page after sign ing #23937

Conversation

bernhardoj commented Jul 31, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jul 31, 2023

bernhardoj commented Jul 31, 2023

allroundexperts commented Jul 31, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

allroundexperts commented Jul 31, 2023

Li357 commented Jul 31, 2023 • edited Loading

bernhardoj commented Aug 1, 2023 • edited Loading

Beamanator commented Aug 1, 2023

allroundexperts commented Aug 1, 2023

allroundexperts commented Aug 1, 2023

bernhardoj commented Aug 2, 2023

allroundexperts left a comment

Choose a reason for hiding this comment

OSBotify commented Aug 2, 2023

OSBotify commented Aug 3, 2023

OSBotify commented Aug 7, 2023

OSBotify commented Aug 7, 2023

OSBotify commented Aug 9, 2023

bernhardoj commented Jul 31, 2023 •

edited

Loading

allroundexperts commented Jul 31, 2023 •

edited

Loading

Li357 commented Jul 31, 2023 •

edited

Loading

bernhardoj commented Aug 1, 2023 •

edited

Loading