Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QBO Export] feat: handling auto-sync errors #45251

Conversation

kosmydel
Copy link
Contributor

@kosmydel kosmydel commented Jul 11, 2024

Details

This PR adds:

  • handling auto-sync errors,
  • the ability to enter credentials when we got logged out from integration.

To enter the credentials I also refactor the integration buttons:

  • buttons are extracted from the connection components,
  • buttons are renamed: ConnectToSageIntacctButton -> ConnectToSageIntacctFlow,
  • a new context AccountingContext is added to run the integration flows centrally,
  • the redirection to upgrade to the control policy screen is now added in the new context,
  • the AccountingConnectionConfirmationModal is now displayed in the context.

Reconnecting on mWeb iOS might not work due to this bug.

Fixed Issues

$ #44016
PROPOSAL: N/A

Tests

Note

The modal animation doesn't work on the Dev environment with Strict Mode. Disable it in CONFIG.ts by settings USE_REACT_STRICT_MODE to false.

Prerequisites

  • Collect workspace with an admin and member
  • Setup QBO (Xero) integration connection

Steps

  1. Log into QBO (Xero) and disconnect the Expensify app: Menu > Apps > Overview > Expensify 3-dot menu > Disconnect (Xero: 9 dots menu > Manage app connections -> Disconnect)
  2. Log into NewDot as the admin
  3. Verify there's an RBR on the path: Avatar > Workspaces > [Workspace name] > Accounting > QBO (Xero)
  4. Verify a red error message appears on the connection explaining the issue
  5. Select QBO's (Xero's) 3-dot menu
  6. Verify there’s a “Enter credentials” option
  7. Select “Enter credentials”
  8. Verify a new window opens to log into QBO (Xero)

Change integration

  1. Go to Accounting settings.
  2. Open Other integrations.
  3. Press connect.
  4. Verify there is a confirmation modal.
  5. Verify the flow is running correctly after pressing Confirm.

Verify new integration connection
All Connect buttons and integration flows were refactored. Verify that it is possible to add each integration:

  • quickbooksOnline,
  • xero,
  • netsuite (set canUseNetSuiteIntegration to true),
  • intact (set canUseSageIntacctIntegration to true).

Verify reusing connections
Do the steps from this PR

Offline tests

N/A

QA Steps

  • Verify that no errors appear in the JS console
  • Do the tests from the above list

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: mWeb Chrome
    • iOS: Native
    • iOS: mWeb 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 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 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 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.

Screenshots/Videos

Android: Native
android-native.mov
Android: mWeb Chrome
android-web.mov
iOS: Native
ios.mp4
iOS: mWeb Safari
MacOS: Chrome / Safari

Xero:

web.mov

All Connect buttons:

Screen.Recording.2024-07-15.at.16.26.58.mov
MacOS: Desktop
desktop.mov

@kosmydel kosmydel force-pushed the @kosmydel/qbo-export/auto-sync-errors branch from 8ba55ba to 5ba1348 Compare July 11, 2024 12:31
@kosmydel kosmydel changed the title feat: handling auto-sync errors [QBO Export] feat: handling auto-sync errors Jul 15, 2024
@kosmydel kosmydel force-pushed the @kosmydel/qbo-export/auto-sync-errors branch from 6ade96e to 1c7f281 Compare July 15, 2024 09:12
@kosmydel kosmydel requested a review from SzymczakJ July 15, 2024 14:33
@kosmydel kosmydel marked this pull request as ready for review July 15, 2024 14:37
@kosmydel kosmydel requested a review from a team as a code owner July 15, 2024 14:37
@melvin-bot melvin-bot bot requested review from arosiclair and ishpaul777 and removed request for a team and SzymczakJ July 15, 2024 14:37
Copy link

melvin-bot bot commented Jul 15, 2024

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

@kosmydel
Copy link
Contributor Author

On mWeb iOS opening reconnecting the integration might not work yet, there will be a separate issue. More details.

@trjExpensify
Copy link
Contributor

@hungvu193 can you take the review of this one with the context on the project? Thanks!

@hungvu193
Copy link
Contributor

Sure thing. Please assign me to this PR. Thank you

@ishpaul777
Copy link
Contributor

Please remove my assignment once @hungvu193 is assiged, Thanks!

@trjExpensify trjExpensify requested review from hungvu193 and removed request for ishpaul777 July 15, 2024 15:34
@hungvu193
Copy link
Contributor

I got this issue while testing and it worked after I refreshed the page few times.

Screen.Recording.2024-07-16.at.14.51.29.mov

@arosiclair
Copy link
Contributor

Found an issue, where the error briefly showed after reconnecting from QBO @war-in

I noticed this while testing as well. There's a delay between IS pushing the last progress update and the final update that sets lastSync.isSuccessful. Let's not block on that problem.

On IOS, pressing Enter credentials doesn't open webview.

I think this should've been fixed by #45762. That's still not the case? cc @zfurtak

On Desktop, I don't see the reconnecting progress after reconnecting is completed.

Is this not an issue on other platforms? I'm actually not sure if the sync should automatically restart after reconnecting.

@zfurtak
Copy link
Contributor

zfurtak commented Aug 13, 2024

On IOS, pressing Enter credentials doesn't open webview.

I think this should've been fixed by #45762. That's still not the case? cc @zfurtak

That's true! 👍

@hungvu193
Copy link
Contributor

hungvu193 commented Aug 13, 2024

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
Screen.Recording.2024-08-13.at.22.57.46.mov
Android: mWeb Chrome
Screen.Recording.2024-08-13.at.11.05.36.mov
iOS: Native
Screen.Recording.2024-08-13.at.22.24.53.mov
iOS: mWeb Safari
safari.mov
MacOS: Chrome / Safari
Screen.Recording.2024-08-13.at.09.45.54.mov
MacOS: Desktop

Uploading Screen Recording 2024-08-13 at 22.46.00.mov…

Copy link
Contributor

@hungvu193 hungvu193 left a comment

Choose a reason for hiding this comment

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

Let's remove these console log 😄

);

const renderActiveIntegration = () => {
console.log('rerender');
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
console.log('rerender');


const renderActiveIntegration = () => {
console.log('rerender');
console.log('activeIntegration', activeIntegration);
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
console.log('activeIntegration', activeIntegration);

@hungvu193
Copy link
Contributor

Is this not an issue on other platforms? I'm actually not sure if the sync should automatically restart after reconnecting.

After re-enter credentials successfully, if I click on Open electron app desktop app will reload and it will work, if I didn't click on it, the connection progress won't be updated. Is that expected?

Screen.Recording.2024-08-13.at.22.46.00.mov

@arosiclair
Copy link
Contributor

Is this not an issue on other platforms? I'm actually not sure if the sync should automatically restart after reconnecting.

After re-enter credentials successfully, if I click on Open electron app desktop app will reload and it will work, if I didn't click on it, the connection progress won't be updated. Is that expected?

I don't think you should expect any progress updates while logging into QBO if that's what you mean. Progress should start after you logged into QBO successfully. Either way, the progress updates are separate from the error handling we're focusing on so let's treat that as a separate issue.

@hungvu193
Copy link
Contributor

I see. Then I think there's only linting left and it will be ready for your final review.

@war-in
Copy link
Contributor

war-in commented Aug 13, 2024

@hungvu193 Logs removed! Sorry for that 😅

@melvin-bot melvin-bot bot requested a review from arosiclair August 13, 2024 17:01
…rors

# Conflicts:
#	src/components/ConnectToQuickbooksOnlineButton/index.native.tsx
#	src/components/ConnectToQuickbooksOnlineButton/index.tsx
Copy link
Contributor

@arosiclair arosiclair left a comment

Choose a reason for hiding this comment

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

Looks pretty good overall just a few questions

};

function AccountingContextProvider({children, policy}: AccountingContextProviderProps) {
const integrationRefs = useRef<Record<string, MutableRefObject<View | null>>>(defaultAccountingContext.integrationRefs.current);
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you help me understand how we're using integrationRefs? I see it initialized with integrationRefsInitialValue but I don't see where it's updated.

Copy link
Contributor

Choose a reason for hiding this comment

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

We're changing integration refs in PolicyAccountingPage to pass the position of the threeDotsMenuContainer button to be able to show modal in the correct place

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh okay I see the name changed to integrationsRef in that file. Lets rename that to popoverAnchorRefs to be a bit more clear. And let's keep the naming consistent in every file.

};

function AccountingContextProvider({children, policy}: AccountingContextProviderProps) {
const integrationRefs = useRef<Record<string, MutableRefObject<View | null>>>(defaultAccountingContext.integrationRefs.current);
Copy link
Contributor

Choose a reason for hiding this comment

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

Oh okay I see the name changed to integrationsRef in that file. Lets rename that to popoverAnchorRefs to be a bit more clear. And let's keep the naming consistent in every file.

…rors

# Conflicts:
#	src/pages/workspace/accounting/PolicyAccountingPage.tsx
@war-in
Copy link
Contributor

war-in commented Aug 19, 2024

@arosiclair Comment addressed and conflicts resolved 🫡

@war-in
Copy link
Contributor

war-in commented Aug 20, 2024

@arosiclair Are we ready for the merge? Or is there something I need to do here? 🤔

@arosiclair
Copy link
Contributor

Nope just got distracted 😄

@arosiclair arosiclair merged commit c62f29f into Expensify:main Aug 20, 2024
15 checks passed
@OSBotify
Copy link
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.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.23-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/chiragsalian in version: 9.0.23-0 🚀

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.

10 participants