-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Pay 4/29][$500] Wallet - No error when clicking Save & continue button after selecting BA with existing draft #38518
Comments
Triggered auto assignment to @MitchExpensify ( |
We think that this bug might be related to #wave-collect - Release 1 |
@MitchExpensify 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. |
ProposalPlease re-state the problem that we are trying to solve in this issue.The add personal bank account page doesn't show an error and just looks like do nothing when pressing the button. What is the root cause of that problem?When we press the save button, we actually request the BE to try saving it, and BE already returns the correct error message for us to show. However, the add personal bank account form has a different key than the BE response. The BE response merges the errors to App/src/pages/AddPersonalBankAccountPage.tsx Lines 82 to 83 in 22bd9eb
Line 408 in 22bd9eb
This happens after this TS migration PR which unnecessarily changes the key. If we look at the bank account step pages, we can see that they don't add App/src/pages/ReimbursementAccount/BankInfo/substeps/Manual.tsx Lines 63 to 64 in 22bd9eb
Line 406 in 22bd9eb
What changes do you think we should make in order to solve the problem?Remove the But after fixing this, we will see the error message shown is still incorrect and this is a separate issue that is being handled here Result after fixing all: Screen.Recording.2024-03-19.at.13.10.58.mov |
Assigning to VSB as this is a personal account issue more in line with off workspace use |
Job added to Upwork: https://www.upwork.com/jobs/~0183d2c7f9a0e1aa53 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @cubuspl42 ( |
Ouch, I reviewed that one. Honestly, I don't understand how this is a regression. The old JS code didn't include the |
I'm not defending the code that introduces the regression, but it's worth noting that all keys in the Could you comment on that? Is this a bigger problem (affecting the whole |
We should definitely figure this out. Right now, both the |
Not all follow the Lines 358 to 359 in d8361ee
Lines 352 to 353 in d8361ee
Lines 418 to 419 in d8361ee
(I think the tax name could use My guess is, that we can't use the |
You're right. Thanks for the extra clarification. I approve the proposal by @bernhardoj |
Current assignee @cubuspl42 is eligible for the External assigner, not assigning anyone new. |
I'm not sure why automation is not assigning an internal engineer to review the assignment of @bernhardoj |
I think @cubuspl42 forget to put the "magic" word |
Sorry! I approve the proposal by @bernhardoj Wait for it... 🥁 C+ reviewed 🎀 👀 🎀 |
Friendly bump @Gonals :) |
Looks good! |
📣 @cubuspl42 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
PR is ready cc: @cubuspl42 |
This issue has not been updated in over 15 days. @cubuspl42, @Gonals, @MitchExpensify, @bernhardoj eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Reminder set to pay on 4/29 Payment summary: $500 Contributor @bernhardoj |
@cubuspl42, @Gonals, @MitchExpensify, @bernhardoj Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Paid and contract ended, apologies for the delay |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.54-0
Reproducible in staging?: y
Reproducible in production?: y
Issue reported by: Applause - Internal Team
Action Performed:
Routing number - 011401533
Account number - 1111222233331111
Expected Result:
App should present an error about unable to proceed with Plaid Saving account (ends with 1111) since there is draft in Step 5.
Actual Result:
There is no error when clicking Save & continue. Nothing happens when clicking on the button.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6418307_1710791246953.20240319_033905.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: