[PAID][$500] Bank account - Different error is displayed on Validate you bank account page

[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.46-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4356707
Email or phone of affected tester (no customers): vdargentotest+web030124@gmail.com
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 Workspace > Bank account
2. Select Manual option
3. Go trough the add BA flow with the testing credentials until you reach the "Validate your bank account" page
4. Enter 3 random amounts (important step)
5. Click on "Validate" button
6. Verify the error is not the expected (Should be "The validate code you entered is incorrect, please try again")
7. Click on "fix the errors"
8. Verify it does not refocus to wrong field

Expected Result:

The error displayed should be "The validate code you entered is incorrect, please try again"

Actual Result:

The error displayed is "Please fix the errors in the form before continuing"

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

Bug6398485_1709312899868.bandicam_2024-03-01_13-01-13-910.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01e383b39945f9cc66
• Upwork Job ID: 1763639802183884800
• Last Price Increase: 2024-03-01

[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 @luacmartins (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[lanitochka17]

@luacmartins FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[luacmartins]

Looking

[luacmartins]

I don't think this is a blocker. We still show an error, just not a generic one instead of the specific error. Gonna demote and make it external