[jnowakow]

Explanation of Change

It restores changes from #56401 that were reverted.

Fixed Issues

$ #52199 (comment)
PROPOSAL: N/A

Tests

Test case 1:

1. Navigate to the bank account connect flow
2. Reach the plaid modal
3. Plaid should point to the Sandbox environment to be able to test it.

Test case 2:

1. Open iOS Hybrid app.
2. Log in with a expensifail account.
3. Tap on: Settings > Workspaces > More features
4. Enable 'Expensify Cards'
5. Go to 'Expensify Cards'
6. Tap on 'Issue card'
7. Assign the card to yourself. Choose a virtual card. Complete the flow.
8. Go to the WS chat
9. Tap on the hyperlink 'Expensify card'
10. The details of the card is displayed.

Test case 3:

1. Launch ND or hybrid app.
2. Go to Account settings.
3. Tap Domains.
4. Domains page will open in external browser.

Test case 4:

1. Launch hybrid app.
2. Log in with a new Expensifail account.
3. Create a new workspace.
4. Go to Concierge chat.
5. Click any task with link in the description (Create a workspace task).
6. Onboarding links are valid and will not show "undefined".

Test case 5:

1. Launch hybrid app.
2. Go to workspace settings > Workflows.
3. Tap Connect bank account.
4. Tap Log into your bank.
5. Select Wells Fargo.
6. Go through Plaid flow on the browser.
7. After completing the Plaid flow, it will land in the app.

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Test case 1:

1. Navigate to the bank account connect flow
2. Reach the plaid modal
3. Plaid should point to the Sandbox environment to be able to test it.

Test case 2:

1. Open iOS Hybrid app.
2. Log in with a expensifail account.
3. Tap on: Settings > Workspaces > More features
4. Enable 'Expensify Cards'
5. Go to 'Expensify Cards'
6. Tap on 'Issue card'
7. Assign the card to yourself. Choose a virtual card. Complete the flow.
8. Go to the WS chat
9. Tap on the hyperlink 'Expensify card'
10. The details of the card is displayed.

Test case 3:

1. Launch ND or hybrid app.
2. Go to Account settings.
3. Tap Domains.
4. Domains page will open in external browser.

Test case 4:

1. Launch hybrid app.
2. Log in with a new Expensifail account.
3. Create a new workspace.
4. Go to Concierge chat.
5. Click any task with link in the description (Create a workspace task).
6. Onboarding links are valid and will not show "undefined".

Test case 5:

1. Launch hybrid app.
2. Go to workspace settings > Workflows.
3. Tap Connect bank account.
4. Tap Log into your bank.
5. Select Wells Fargo.
6. Go through Plaid flow on the browser.
7. After completing the Plaid flow, it will land in the app.

• 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: 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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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.ts 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.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• 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: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

[melvin-bot]

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

[ZhenjaHorbach]

@jnowakow
Do you need help with a review ?

[jnowakow]

@ZhenjaHorbach I think it would be good to trigger adhoc builds and test this PR that earlier there were some issues . I wasn't able to reproduce them locally.
cc @AndrewGable @Julesssss

[ZhenjaHorbach]

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 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.ts 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.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
• 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

NA

Android: mWeb Chrome

NA

iOS: Native

2025-02-18.15.00.40.mp4

2025-02-18.15.00.36.mp4

2025-02-18.15.20.40.mp4

iOS: mWeb Safari

NA

MacOS: Chrome / Safari

NA

MacOS: Desktop

NA

[ZhenjaHorbach]

@ZhenjaHorbach I think it would be good to trigger adhoc builds and test this PR that earlier there were some issues . I wasn't able to reproduce them locally. cc @AndrewGable @Julesssss

Agree that it is better to test this PR using adhoc builds !

@mountiny
Maybe you are free to trigger builds? 😀

[github-actions]

🚧 @mountiny has triggered a test hybrid app build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/57015/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/57015/index.html
Desktop 💻	Web 🕸️
N/A	N/A
N/A	N/A

---

👀 View the workflow run that generated this build 👀

[jnowakow]

@mountiny can you ask testers to examine the builds? More issues are on iOS and I don't have access to one

[mountiny]

@jnowakow can you list all the test steps in the PR body so I can just link the PR to them?

[jnowakow]

@mountiny updated :D

[mountiny]

Asked QA https://expensify.slack.com/archives/C9YU7BX5M/p1739886537092349

[ZhenjaHorbach]

Just tested IOS
None of issues are reproduced !

And left only one issue for android to test
But for some reason I constantly see the same error as here

[vincdargento]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Workspace - Connect BA - Error message appears when try to add BA via Plaid modal

Version Number: v.9.1.0-0 PR:57015 Ad-Hoc
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause Internal Team

Action Performed:

1. Open the Ad-Hoc App
2. Login with any account
3. Go to Settings -> Open any WS (create it if needed) -> Workflows -> Add approval workflow
4. Change currency to USD
5. Choose Plaid and enter a magic code

Expected Result:

You can continue the flow of adding BA

Actual Result:

Error message arrears and cannot procced the flow

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

[jnowakow]

This issue seems to be not related. It seems that there is limit on how many times you can go through Plaid's flow. Even in sandbox environment

[mountiny]

Seems like we are good then! @jnowakow can you please update the PR title?

[mountiny]

@ZhenjaHorbach can you complete the checklist please?

[ZhenjaHorbach]

@ZhenjaHorbach can you complete the checklist please?

Done !
And LGTM !

[jnowakow]

@mountiny done! 🫡

[jnowakow]

One more thing. @mountiny can you check in Plaid's dashboard which android package is registered?

[mountiny]

Hmm never had to go there, asking around. Any reason you asking? seems like Plaid is working fine so I guess its correctly setup

[jnowakow]

Earlier there was com.expensify.chat hardcoded so I want to be sure that Plaid's configuration match reality. Now actual package name will be passed so this should fix this issue on staging. I want to be sure that there's package name for production hybrid app which is org.me.mobiexpensifyg.
It worked before even though there was mismatch but I think it would be good to adjust package names in console

[ZhenjaHorbach]

Actually just tested another adhoc build
And I don't have this issue on android

[jnowakow]

Hmm actually I just noticed that the issue with disabled login is caused by package mismatch

[jnowakow]

This would mean that #56719 is reproducible on production 🤔

[mountiny]

It might be, we dont have testing account for production so real data would have to be used to confirm

[jnowakow]

Okey, so I think it's reasonable to add package names that match hybrid app

[OSBotify]

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

[github-actions]

🚀 Deployed to staging by https://github.com/AndrewGable in version: 9.1.2-0 🚀

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

[izarutskaya]

PR is failing on Android with #57152 and
failing on iOS with issues: #57148, #57149, #57150

1740021243345.57015_iOS_-_Test_1.mp4

1740022302909.57015_iOS_-_Test_4.mp4

Pending validation on Desktop

[jnowakow]

Fix for all three iOS issues is here.
Fix for Android requires changes in Plaid's dashboard

[izarutskaya]

@jnowakow Tester can reproduce the issue #52199 on IOs
Can you please check the video and let me know? Thank you

1740021243345.57015_iOS_-_Test_1.1.mp4

[jnowakow]

@izarutskaya this should be fixed by https://github.com/Expensify/Mobile-Expensify/pull/13433 as well

[github-actions]

🚀 Deployed to production by https://github.com/francoisl in version: 9.1.2-1 🚀

platform	result
🤖 android 🤖	true ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	failure ❌