BA - VBA can not be added either via plaid or manually. Need to verify info via chat.

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.95-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check, can't add BA on prod
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5568853, https://expensify.testrail.io/index.php?/tests/view/5568474
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: MacOS 14.7.2 / Safari, Chrome, Desktop
App Component: Workspace Settings

Action Performed:

1. Go to staging.new.expensify.com or open Desktop App
2. Login with new Expensifail account
3. Create workspace and enable workflow
4. Go to Workspace > Workflows > Connect Bank Account
5. Select Plaid or Manual method
6. Follow the flow

Expected Result:

VBA can not be added via Plaid. User goes to a validation page when adding manually.

Actual Result:

VBA can not be added either via plaid or manually. User receives an offer to verify information in the chat.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6735738_1738887379861.Desktop-VBA-cannot-finish.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @mjasikowski (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[mjasikowski]

Can't reproduce on dev, seems to be staging backend related

[mjasikowski]

Asked on slack whether there was any recent changes to the VBA flow that could trigger this

[mjasikowski]

@IuliiaHerets Can you please retest? this should be fixed now, there was a problem with VBA validation