-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] Bank account - Different error message for incorrect validation amounts #46628
Comments
Triggered auto assignment to @johncschuster ( |
@johncschuster 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 |
We think that this bug might be related to #wave-collect - Release 1 |
ProposalPlease re-state the problem that we are trying to solve in this issue.Bank account - Different error message for incorrect validation amounts What is the root cause of that problem?The root cause is that the response from
However, on the front end, we use App/src/pages/ReimbursementAccount/ConnectBankAccount/components/BankAccountValidationForm.tsx Line 94 in e36fcce
App/src/libs/actions/BankAccounts.ts Lines 332 to 338 in b0ca6ad
What changes do you think we should make in order to solve the problem?We should bring the backend validation of the input amounts to the front end to allow the front end to validate the amount of input before sending it to the backend. If this is possible, it would be reasonable especially offline. What alternative solutions did you explore? (Optional)From the backend, we stop sending back the secondary error message when the amount is invalid and depends on the error message used in the front end. App/src/libs/actions/BankAccounts.ts Line 338 in b0ca6ad
|
Job added to Upwork: https://www.upwork.com/jobs/~01a0f2937fb2d6512f |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee ( |
@jjcoffee, Yeah, the backend is returning a different error message. |
Sounds like a BE fix is required here then @johncschuster 🙏 |
@johncschuster @jjcoffee this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Issue not reproducible during KI retests. (First week) |
This is deployed, we can close it. |
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: 9.0.15-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Issue found when executing PR #45732
Action Performed:
Expected Result:
The error message will be "The validation amounts you entered are incorrect. Please double-check your bank statement and try again
Actual Result:
The error message is "The validate code you entered is incorrect, please try again
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @jjcoffeeThe text was updated successfully, but these errors were encountered: