Closed izarutskaya closed 1 week ago
Triggered auto assignment to @dylanexpensify (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
: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 @chiragsalian (Engineering
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
@chiragsalian 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.
commented here
I'm pretty sure this is external since it's happening only on mWeb. Assigning external label.
Job added to Upwork: https://www.upwork.com/jobs/~01a531e07d9e5f1c52
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra (External
)
Not able to add Regions BA, modal redirects to initial Bank account page
The PlaidLink
opens the connection multiple times because of the following useEffect
, since the onError
is a function that doesn't have dependencies causing it to rerender:
https://github.com/Expensify/App/blob/8aec07c55df3f0fefc6bed76c991183cf6b97f7a/src/components/PlaidLink/index.tsx#L39-L54
there is no need to add the onError
to the dependency list of the useEffect
since we already have the error
object inside the dependencies list so it should call the useEffect
in case the error
changes:
// eslint-disable-next-line react-hooks/exhaustive-deps
}, [ready, error, isPlaidLoaded, open]);
this way the Plaid
component behaviour will be consistent and the useEffect
will not depend on whether the incoming onError
prop has a dependencies list or not
also, we can remove the open
function from the dependencies as well since we don't know what the dependencies of this function but this step is optional in solving our issue
https://github.com/Expensify/App/assets/59809993/33c90dcb-aeee-4db6-8c89-711796318853
@abzokhattab Can you mark the offending PR as this is deploy blocker?
Does that mean its not occurring on production? As far as i can see we were not able to test it on prod
Thanks, honestly I am not able to find it i just checked the differences between staging
and production
and I see that all the changes are not related to the bank setup.
https://github.com/Expensify/App/compare/production...staging
let me know if you are able to find any
Can you confirm the repro of the issue on staging? And on https://36676.pr-testing.expensify.com/
Lets go with @abzokhattab's proposal.
πππ C+ reviewed
Current assignee @chiragsalian is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new.
Proposal LGTM. Feel free to create the PR for this @abzokhattab. Try to prioritize this since we'll have to try to get it reviewed/merged and CP'd soon since the issue is a blocker.
π£ @shubham1206agra π An offer has been automatically sent to your Upwork account for the Reviewer role π Thanks for contributing to the Expensify app!
π£ @abzokhattab π An offer has been automatically sent to your Upwork account for the Contributor role π Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review π§βπ» Keep in mind: Code of Conduct | Contributing π
Thanks!! the PR is ready.
We're demoting this to NAB since we could reproduce the same issue on this adboc build that was deployed to prod 5 days ago. We think this is a Plaid issue on their sandbox API.
Most likely related to https://github.com/Expensify/App/issues/32356
Would you like to post a proposal here?
I already have a proposal there
@bernhardoj Please create a test branch to confirm the proposal fixes this issue too. Thanks
Moving along!
Proposal is updated
@dylanexpensify Can you unassign @abzokhattab here and reopen this for proposals?
@shubham1206agra I don't know if it's the same issue or not because, in https://github.com/Expensify/App/issues/32356, the connect option page is shown for a few seconds before showing the correct step,
but in the OP video, looks like the correct step is never shown and I can't reproduce that.
You can test it here: https://github.com/bernhardoj/Expensify/tree/fix/plaid-reopening-on-rerender
Hey, I've been looking into this issue as it relates to Callstack's recent VBBA refactor to see if it's a regression issue.
It seems the problem is with the unstable ref for PlaidLink
βs onError
prop and actually @bernhardoj's suggestion here describes the problem well and it was posted way back in December last year so kudos to him. In my testing this solves the issue (tried both, Regions and CitiBank)
cc @dylanexpensify @shubham1206agra @luacmartins
Can confirm, https://github.com/bernhardoj/Expensify/tree/fix/plaid-reopening-on-rerender fixed the issue.
@chiragsalian @luacmartins Can we assign @bernhardoj to fix the issue here as other PR has no activity for quite some time?
That sounds good to me, but I'll let @chiragsalian handle this since he's the assigned engineer on this issue
Yup that sounds good to me. Feel free to create a PR @bernhardoj.
β There was an error making the offer to @bernhardoj for the Contributor role. The BZ member will need to manually hire the contributor.
PR is ready
cc: @shubham1206agra
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 1.4.54-4 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-03-26. :confetti_ball:
For reference, here are some details about the assignees on 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:
Payment coming up!
paying out today!
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:
@dylanexpensify I have discussed this internally here. You may close this issue when you issue the payment to other contributor as I am keeping track of payment internally and will ask to pay once the issue is resolved. Just write in the payment summary that I have not been paid yet.
Payment summary:
Please apply/request!
@bernhardoj please accept offer when ready and I'll pay it out!
@dylanexpensify the offer is broken.
oh weird! Let me send a new one then!
@bernhardoj sent an invite to apply!
@dylanexpensify applied
@bernhardoj sent!
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: v1.4.50-2 Reproducible in staging?: Y Reproducible in production?: Unable to check If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4413762 Email or phone of affected tester (no customers): applausetester+vd_mweb031124@applause.expensifail.com Logs: https://stackoverflow.com/c/expensify/questions/4856 Issue reported by: Applause-Internal team
Action Performed:
Pre-requisite: user must be logged in on mWeb/Safari (iPhone) and must have created a Workspace.
Expected Result:
The page to confirm the account should be displayed.
Actual Result:
The modal redirects to the initial add bank account page.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/5dc83ec7-74ff-4f7f-886c-c99a656f869c
View all open jobs on GitHub
Upwork Automation - Do Not Edit