You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-08-09] [$250] Bank account - No error message is displayed for incorrect validation amounts #45246
changed the title [-]Bank account - No error message is displayed for incorrect validation amounts[/-][+][$250] Bank account - No error message is displayed for incorrect validation amounts[/+]on Jul 11, 2024
What changes do you think we should make in order to solve the problem?
Add a if block which will compare max/min amount with filteredValue and add error using errors[key as keyof AmountValues] = translate('common.error.invalidAmount');. Error message can be created or can be used from any other form.
What alternative solutions did you explore? (Optional)
We don't set the errors, so when the data returned by the back-end does not have the errors set, like in the case of 402 error code (back-end temporary issue) here, no errors will be shown to the users and it looks like the app is not responsive and broken.
What changes do you think we should make in order to solve the problem?
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.15-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@hungvu193] The PR that introduced the bug has been identified. Link to the PR:
[@hungvu193] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@hungvu193] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@hungvu193] Determine if we should create a regression test for this bug.
[@hungvu193] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@abekkala] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
Determine if we should create a regression test for this bug: Yes
Regression test:
Go to Settings > Workspaces > Workspace > Workflows.
Tap on "Connect bank account".
Select "Connect manually" or "Connect with Plaid".
Go through the add bank account process using the testing credentials.
Once you reach the "Validate your bank account" page, enter 3 random amounts and click on the "Validate" button.
Submit many times.
Verify that the error message display at the bottom of the page.
Activity
melvin-bot commentedon Jul 11, 2024
Triggered auto assignment to @abekkala (
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.izarutskaya commentedon Jul 11, 2024
We think this issue might be related to the #collect project.
[-]Bank account - No error message is displayed for incorrect validation amounts[/-][+][$250] Bank account - No error message is displayed for incorrect validation amounts[/+]melvin-bot commentedon Jul 11, 2024
Job added to Upwork: https://www.upwork.com/jobs/~016e89ad61491fffbc
melvin-bot commentedon Jul 11, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (
External)Krishna2323 commentedon Jul 11, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
Bank account - No error message is displayed for incorrect validation amounts
What is the root cause of that problem?
No validation is added for amount limit.
App/src/pages/ReimbursementAccount/ConnectBankAccount/components/BankAccountValidationForm.tsx
Lines 65 to 81 in 3fd1644
What changes do you think we should make in order to solve the problem?
Add a if block which will compare max/min amount with
filteredValueand add error usingerrors[key as keyof AmountValues] = translate('common.error.invalidAmount');. Error message can be created or can be used from any other form.What alternative solutions did you explore? (Optional)
Krishna2323 commentedon Jul 11, 2024
@izarutskaya @abekkala, is there any min/max limit for these inputs? When we should throw an error? I don't understand the bug exactly.
tienifr commentedon Jul 12, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
The error message for incorrect validation amounts is not displayed. Also, the validation is not disabled due to many tries.
What is the root cause of that problem?
In failure data of
VALIDATE_BANK_ACCOUNT_WITH_TRANSACTIONSinApp/src/libs/actions/BankAccounts.ts
Line 336 in 58e2575
We don't set the
errors, so when the data returned by the back-end does not have theerrorsset, like in the case of 402 error code (back-end temporary issue) here, noerrorswill be shown to the users and it looks like the app is not responsive and broken.What changes do you think we should make in order to solve the problem?
Add optimistic errors for code validation similar to the approach here https://github.com/Expensify/App/blob/main/src/libs/actions/BankAccounts.ts#L165
In this add
What alternative solutions did you explore? (Optional)
Store only the error translation key in Onyx, and use
translateto translate it when we display the error26 remaining items
melvin-bot commentedon Aug 2, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.15-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-08-09. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Aug 2, 2024
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
abekkala commentedon Aug 2, 2024
PAYMENT SUMMARY FOR AUG 09, if no regressions
please complete checklist
abekkala commentedon Aug 8, 2024
not overdue payment is tomorrow
hungvu193 commentedon Aug 9, 2024
Regression test:
Do we 👍 or 👎 ?
abekkala commentedon Aug 9, 2024
PAYMENT SUMMARY FOR AUG 09, if no regressions
JmillsExpensify commentedon Aug 14, 2024
$250 approved for @hungvu193
garrettmknight commentedon Sep 4, 2024
$250 approved for @tienifr