[HOLD for payment 2023-04-04] Workspace -Unable to add Chase bank account, can't choose a bank account ending in 1111/0000

[kbecciv]

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

---

Action Performed:

1. Go to URL https://staging.new.expensify.com/
2. Login with any account
3. Go to Settings -> Workspaces -> Open any WS -> Connect bank account -> Connect online with Plaid
4. On the bank account list select "Chase"
5. Enter the credentials "user_good / pass_good" in "First Platypus Bank"
6. Select mobile and enter "credentials_good" as the verification mode
7. Checkmark the "Plaid Checking" and "Plaid Saving"
8. Checkmark the 2 options under "additional information you want to share" -> Click on continue
9. Click "Connect account information"
10. Click on the last confirmation on the plaid modal
11. Select the bank account ending in 1111

Expected Result:

Unable to add Chase bank account, can't choose a bank account ending in 1111/0000

Actual Result:

The bank account ending in 1111 was selected and Chase bank account added successfully

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.90.6

Reproducible in staging?: Yes

Reproducible in production?: Unable to verify

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5995087_Recording__4041.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 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.