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
We're painfully aware of that - this change in React 18 has caused us nothing but grief. We've lost many days chasing down the obscure issues it has caused in third-party components. I understand why they made the change, but I think it will just drive people to stop using <StrictMode>, which is counter-productive.
We're painfully aware of that - this change in React 18 has caused us nothing but grief. We've lost many days chasing down the obscure issues it has caused in third-party components. I understand why they made the change, but I think it will just drive people to stop using , which is counter-productive.
I also spent countless hours chasing my tail on this one. For that reason and some other minor issues I don't use it anymore.
In React 18, <React.StrictMode> renders twice when in dev mode to detect unintended side-effects:
https://reactjs.org/docs/strict-mode.html#detecting-unexpected-side-effects
This results in the pop-up being created twice, which causes issues for some types of pop-up (OAuth).
The text was updated successfully, but these errors were encountered: