Skip to content
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

Closed
6 tasks done
lanitochka17 opened this issue Aug 1, 2024 · 12 comments
Closed
6 tasks done
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Internal Requires API changes or must be handled by Expensify staff Reviewing Has a PR in review Weekly KSv2

Comments

@lanitochka17
Copy link

lanitochka17 commented Aug 1, 2024

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:

  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Workflows
  3. Click Connect bank account
  4. Click Connect manually
  5. Proceed to "Validate your bank account" step
  6. Enter incorrect amount for each transaction value
  7. Click Validate

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?

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

Screenshots/Videos

Add any screenshot/video evidence

6 10 02

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01a0f2937fb2d6512f
  • Upwork Job ID: 1820565013326918810
  • Last Price Increase: 2024-08-05
Issue OwnerCurrent Issue Owner: @jjcoffee
@lanitochka17 lanitochka17 added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Aug 1, 2024
Copy link

melvin-bot bot commented Aug 1, 2024

Triggered auto assignment to @johncschuster (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.

@lanitochka17
Copy link
Author

@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

@lanitochka17
Copy link
Author

We think that this bug might be related to #wave-collect - Release 1

@Tony-MK
Copy link
Contributor

Tony-MK commented Aug 1, 2024

Proposal

Please 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 WRITE_COMMANDS.VALIDATE_BANK_ACCOUNT_WITH_TRANSACTIONS is not 'bankAccount.error.validationAmounts' and merges a different response error message but this.

"The validate code you entered is incorrect, please try again"

Screenshot 2024-08-01 at 20 35 53

However, on the front end, we use 'bankAccount.error.validationAmounts' when handling the BankAccountValidationForm error.

BankAccounts.validateBankAccount(bankAccountID, validateCode, policyID);

failureData: [
{
onyxMethod: Onyx.METHOD.MERGE,
key: ONYXKEYS.REIMBURSEMENT_ACCOUNT,
value: {
isLoading: false,
errors: ErrorUtils.getMicroSecondOnyxErrorWithTranslationKey('bankAccount.error.validationAmounts'),

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.

errors: ErrorUtils.getMicroSecondOnyxErrorWithTranslationKey('bankAccount.error.validationAmounts'),

@melvin-bot melvin-bot bot added the Overdue label Aug 5, 2024
@johncschuster johncschuster added the External Added to denote the issue can be worked on by a contributor label Aug 5, 2024
Copy link

melvin-bot bot commented Aug 5, 2024

Job added to Upwork: https://www.upwork.com/jobs/~01a0f2937fb2d6512f

@melvin-bot melvin-bot bot changed the title Bank account - Different error message for incorrect validation amounts [$250] Bank account - Different error message for incorrect validation amounts Aug 5, 2024
@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Aug 5, 2024
Copy link

melvin-bot bot commented Aug 5, 2024

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

@melvin-bot melvin-bot bot removed the Overdue label Aug 5, 2024
@jjcoffee
Copy link
Contributor

jjcoffee commented Aug 6, 2024

@Tony-MK Thanks for your proposal! Just to clarify, are you saying that the BE is returning the incorrect error The validate code you entered is incorrect, please try again?

@Tony-MK
Copy link
Contributor

Tony-MK commented Aug 6, 2024

@jjcoffee, Yeah, the backend is returning a different error message.

@jjcoffee
Copy link
Contributor

jjcoffee commented Aug 6, 2024

Sounds like a BE fix is required here then @johncschuster 🙏

@trjExpensify trjExpensify added Internal Requires API changes or must be handled by Expensify staff and removed External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors labels Aug 9, 2024
@trjExpensify trjExpensify added Hot Pick Ready for an engineer to pick up and run with and removed Daily KSv2 Overdue labels Aug 9, 2024
@melvin-bot melvin-bot bot added the Monthly KSv2 label Aug 9, 2024
Copy link

melvin-bot bot commented Aug 15, 2024

@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!

@garrettmknight garrettmknight added Weekly KSv2 and removed Monthly KSv2 labels Aug 19, 2024
@rlinoz rlinoz self-assigned this Aug 19, 2024
@rlinoz rlinoz removed the Hot Pick Ready for an engineer to pick up and run with label Aug 19, 2024
@luacmartins luacmartins added the Reviewing Has a PR in review label Aug 19, 2024
@garrettmknight garrettmknight moved this from HOT PICKS to Release 2: Summer 2024 (Aug) in [#whatsnext] #wave-collect Aug 20, 2024
@mvtglobally
Copy link

Issue not reproducible during KI retests. (First week)

@rlinoz
Copy link
Contributor

rlinoz commented Aug 23, 2024

This is deployed, we can close it.

@rlinoz rlinoz closed this as completed Aug 23, 2024
@github-project-automation github-project-automation bot moved this from Release 2: Summer 2024 (Aug) to Done in [#whatsnext] #wave-collect Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Internal Requires API changes or must be handled by Expensify staff Reviewing Has a PR in review Weekly KSv2
Projects
No open projects
Status: Done
Development

No branches or pull requests

9 participants