[$500] BA - Error message for wrong account number does not appear, unexpected error instead

[lanitochka17]

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

---

Version Number: 1.4.34-1
Reproducible in staging?: Y
Reproducible in production?: Not able to test on production
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4255853
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

Pre-requisite: user must be logged in and have created a Workspace

1. Go to Settings > Workspaces > Select Workspace > Bank account
2. Select "Connect online with Plaid"
3. Go trough the add bank account process, select Chase and the account ending with 1111
4. Enter the Routing number
5. On the account number field, enter "1111222233334444"
6. Click on "Continue"

Expected Result:

An error message should be displayed: "Your account number should end with 1111"

Actual Result:

Another error message is displayed: "An unexpected error occurred while trying to add your bank account. Please try again": An unexpected error occurred while trying to add your bank account. Please try again.

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6362939_1706737360781.bandicam_2024-01-31_14-28-31-607.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01665cdc2655d7f614
• Upwork Job ID: 1752870011138125824
• Last Price Increase: 2024-02-01

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01665cdc2655d7f614

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (External)

[melvin-bot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

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

[melvin-bot]

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

[marcaaron]

An error message should be displayed: "Your account number should end with 1111"

confirming: This is the expected behavior? Why would this error say that? 🤔

[marcaaron]

Ok error looks like it would be thrown from here. I see @Gonals and @MariaHCD in some git blames (quite old though) so maybe they have some context or an idea about what to look at next.

On first glance, I don't see any changes in the current staging App checklist that might cause this.

[Gonals]

Ok error looks like it would be thrown from here. I see @Gonals and @MariaHCD in some git blames (quite old though) so maybe they have some context or an idea about what to look at next.

On first glance, I don't see any changes in the current staging App checklist that might cause this.

Heh. That was a while ago 😅. I don't really recall much of it off the top of my head, but I agree this doesn't seem like a blocker

[parasharrajat]

I am curious why we have to manually enter the routing number and account number when we already fetched those via Plaid and then got the selection from the user.

I agree, it doesn't have to be a deploy blocker.

[mountiny]

If we decide this is not a deploy blocker, I think we can close this/ put on hold for the bank account flow refactor which will update lots of the patterns here #34498

[mountiny]

@marcaaron @nkuoch Actually I think Nathalie fixed it with https://github.com/Expensify/Web-Expensify/pull/40755/files

[mountiny]

Or maybe not that fix is only in the new flow if I see correctly

[marcaaron]

Ah thanks everyone! ❤️

[nkuoch]

Weird, can't reproduce in dev nor staging

@lanitochka17 What email did you use, so I can check the logs?

[melvin-bot]

@nkuoch, @johncschuster, @parasharrajat, @marcaaron Whoops! This issue is 2 days overdue. Let's get this updated quick!

[lanitochka17]

@nkuoch Hello
applausetester+vd_web013124@applause.expensifail.com

[johncschuster]

@nkuoch bump!

[nkuoch]

@lanitochka17 Didn't find anything obvious from the logs, and still cannot reproduce it. @lanitochka17 Are you sure you can reproduce it?

I can't:
https://github.com/Expensify/App/assets/2463975/33db890a-3c15-4168-810d-f22dc88cb074

Closing, please reopen if you can reproduce it.

[lanitochka17]

@nkuoch Issue is not reproducible