Closed kbecciv closed 8 months ago
:wave: 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:
Triggered auto assignment to @marcaaron (Engineering
), see https://stackoverflow.com/c/expensify/questions/4319 for more details.
Seems a backend issue where for wallet OpenPlaidBankAccountSelector
api it sets the unwanted reimbursementAccount BankAccountStep
data.
As OpenPlaidBankAccountSelector
common for reimbursementAccount bank account setup and wallet bank account flow, we can pass an extra param which can help to decide whether to set reimbursementAccount BankAccountStep
or not.
Seems a backend issue where for wallet OpenPlaidBankAccountSelector api it sets the unwanted reimbursementAccount BankAccountStep data
This is an old change though (~ 1 year) so I would guess either the same happens on production or a more recent frontend change causes this.
A code comment says:
If there are accounts, then return the processed list of bank accounts as well as the owners in case of withdrawal setup.
Sounds like the expectation is that we would just land in the Add bank account page with the accounts already available in the selector? cc @nkuoch who might remember for sure.
The frontend for this has not been changed since the last deploy so I think this is a non-blocker. The last material changed looks to be here. So, maybe we introduced some regression about how this works.
Triggered auto assignment to @peterdbarkerUK (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
Platforms
in OP are ✅)⚠️ Looks like this issue was linked to a Deploy Blocker here
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
@peterdbarkerUK Eep! 4 days overdue now. Issues have feelings too...
@peterdbarkerUK Huh... This is 4 days overdue. Who can take care of this?
Coming from here - this is expected behaviour.
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.21.1 Reproducible in staging?: y Reproducible in production?: Team can not verify production If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs: https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: Applause - Internal Team Slack conversation:
Action Performed:
Expected Result:
Plaid process shouldn't start without clicking on it's button.
Actual Result:
Plaid process auto starts after adding a personal bank account.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/be51e2ff-732e-402f-967c-799a11d4dc43
View all open jobs on GitHub