Skip to content

Clear iouReportID param in the report Onyx key after an IOU is successfully paid#16624

Merged
Gonals merged 2 commits into
mainfrom
maria-clear-iou-report-id
Apr 12, 2023
Merged

Clear iouReportID param in the report Onyx key after an IOU is successfully paid#16624
Gonals merged 2 commits into
mainfrom
maria-clear-iou-report-id

Conversation

@MariaHCD

@MariaHCD MariaHCD commented Mar 28, 2023

Copy link
Copy Markdown
Contributor

The IOU report ID is not cleared in Onyx after paying, so we try to add a IOU new request to the existing, closed report which results in a 400 Unique Constraints Violation on the backend. Let's clear the iouReportID in Onyx in the successData of PayMoneyRequest

Details

Fixed Issues

$ #16105
PROPOSAL: GH_LINK_ISSUE(COMMENT)

Tests

Prerequisites:
Account A: Account with either a silver/pending or a gold/activated wallet
Account B: Account with a gold/activated wallet

  1. Login to NewDot with as Account A
  2. Request money from Account B
  3. As Account B, pay the request via Expensify
  4. As Account A, send another request for money from Account B
  5. Verify there is no error when requesting money

Offline tests

Requesting money when offline should create the IOU in the pending state:

Screenshot 2023-03-28 at 3 48 53 PM

QA Steps

Verify that requesting money from another account multiple times works as expected

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 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 correct English and 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
    • 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 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-03-28.at.3.44.30.PM.mov
Mobile Web - Chrome
XRecorder_29032023_155013.mp4
Mobile Web - Safari
Screen.Recording.2023-03-29.at.3.27.20.PM.mov
Desktop
Screen.Recording.2023-03-28.at.3.53.46.PM.mov
iOS
Screen.Recording.2023-03-29.at.3.23.50.PM.mov
Android Screenshot 2023-03-29 at 3 40 55 PM

@MariaHCD MariaHCD marked this pull request as ready for review March 29, 2023 15:58
@MariaHCD MariaHCD requested a review from a team as a code owner March 29, 2023 15:58
@melvin-bot melvin-bot Bot requested review from fedirjh and thienlnam and removed request for a team March 29, 2023 15:59
@MelvinBot

Copy link
Copy Markdown
Contributor

@fedirjh @thienlnam One of you needs to 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]

@MariaHCD

Copy link
Copy Markdown
Contributor Author

@fedirjh I don't think you'll be able to test this since this requires a gold/activated wallet.

@thienlnam thienlnam removed the request for review from fedirjh March 29, 2023 16:55
@MariaHCD

MariaHCD commented Apr 4, 2023

Copy link
Copy Markdown
Contributor Author

Friendly bump on reviews @Gonals @thienlnam 🙏🏼

@thienlnam thienlnam left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change looks good, but can't run through the checklist screenshots right now 😢
This is a pretty small change though so not too worried about it failing

@MariaHCD MariaHCD requested a review from a team April 5, 2023 15:36
@MariaHCD

MariaHCD commented Apr 5, 2023

Copy link
Copy Markdown
Contributor Author

I think @Gonals is going to be ooo for the rest of the week so tagging pullerbear again for review + tests 🙏🏼

@melvin-bot melvin-bot Bot requested review from Julesssss and Santhosh-Sellavel and removed request for a team April 5, 2023 15:37
@MelvinBot

Copy link
Copy Markdown
Contributor

@Santhosh-Sellavel @Julesssss One of you needs to 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]

@MariaHCD MariaHCD removed the request for review from Santhosh-Sellavel April 5, 2023 15:37
@MariaHCD

MariaHCD commented Apr 5, 2023

Copy link
Copy Markdown
Contributor Author

Gold/activated wallets aren't available for contributors so @Santhosh-Sellavel can't test this, unfortunately.

@thienlnam

thienlnam commented Apr 5, 2023

Copy link
Copy Markdown
Contributor

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 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 correct English and 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 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

Screenshot 2023-04-11 at 14 49 53

Mobile Web - Chrome

android-

Mobile Web - Safari

Simulator Screen Shot - iPhone 14 Pro - 2023-04-11 at 14 59 08

Desktop Screenshot 2023-04-11 at 15 04 50
iOS
Android

@thienlnam

Copy link
Copy Markdown
Contributor

@Julesssss Sorry, my simulators are broken right now - could you please test the ios / android native? I can complete the rest of the platforms

@Julesssss

Julesssss commented Apr 6, 2023

Copy link
Copy Markdown
Contributor

Hey all, I'm sorry but I ran out of time today to test this on iOS/Android. This was one of 16 items on my 10am todo list and I didn't quite have time for everything 😞

It's still at the top of my list, but we have a 4 day bank holiday in the UK starting tomorrow. If you are happy to wait until Tuesday I can test both native Android and iOS. Hope that's not too annoying!

@MariaHCD

MariaHCD commented Apr 7, 2023

Copy link
Copy Markdown
Contributor Author

No worries, @Julesssss! This feature is behind a beta so this bug shouldn't be affecting too many people right now.

@Julesssss

Copy link
Copy Markdown
Contributor

Okay, I'm back and trying to run through the steps. I get stuck here though, as I'm prompted to add additional details via Onfido as my silver wallet user. Is there a way to avoid this check? (userA has a gold wallet, userB has a silver wallet added via the cliTools add bank account script):

Pay via Expensify as Account B

Screenshot 2023-04-11 at 11 31 42

@MariaHCD

MariaHCD commented Apr 11, 2023

Copy link
Copy Markdown
Contributor Author

@Julesssss Oh, sorry, I think my instructions are a bit off, Account B should be the one with a Gold/Activated wallet 😅

I've updated the test steps to be more clear.

@Julesssss Julesssss left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With @MariaHCD's help I was able to configure the wallet correctly. Unfortunately, the issue is still occuring for me on iOS, which is quite confusing... I can see Maria was successful, but even after a fresh install I'm seeing the error 😖

I'm also struggling to get Android to build on my new machine.

Screen.Recording.2023-04-11.at.15.25.52.mov

I have verified on all platforms except native and added the screenshots.

@Julesssss

Copy link
Copy Markdown
Contributor

Finished configuring my Android emulator and I'm seeing the same issue. It seems odd that this only occurs on native :/

Screenshot 2023-04-11 at 17 02 26

I see that Maria didn't have this problem originally... @thienlnam have you been able to configure iOS/Android in the meantime? It would be good to determine whether this is just an issue on my end or not.

@thienlnam

Copy link
Copy Markdown
Contributor
Screen.Recording.2023-04-11.at.5.27.05.PM.mov

So I fixed my ios simulator.. but android is still borked. It seems to be working fine for me. I added the recording just so you can check that I'm doing it correctly

@thienlnam thienlnam left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can move forward with merging since it's working for me in IOS at least - will leave the final call up to you all

@Julesssss

Copy link
Copy Markdown
Contributor

I'm going to try one last time this morning after updating all repos.

@Gonals Gonals merged commit 5d69c8e into main Apr 12, 2023
@Gonals Gonals deleted the maria-clear-iou-report-id branch April 12, 2023 10:16
@OSBotify

Copy link
Copy Markdown
Contributor

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

@Julesssss Julesssss left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I'm still confused, but I located the error and it doesn't seem related to the changes:

Screenshot 2023-04-12 at 11 35 19

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/Gonals in version: 1.3.0-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.0-2 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants