-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
Uncaught Invariant Violation: Unable to find node on an unmounted component error occurred in the <Transition> component #16273
Comments
This may be caused by reactjs/react-transition-group#469 We're in the process of setting up a fork that works without findDOMNode. Hopefully this resovles those issues. |
i think this bug is from functional components , i use functions and before that , i have no errors |
Out of curiosity: Do you even use transition handlers e.g. |
it is my Drawer
|
You could've also passed your own |
@nimahkh By any chance, can you provide a minimal reproduction example? |
|
@nimahkh Could you provide a minimal reproduction? We won't be able to help more otherwise. |
i was writing in codesandbox and then it crash and throw me out . but something is interesting , my code works on sandbox , i dont know what is going on |
solvedit was because of lazy and suspense . i dont know why , but when i remove suspense and load components normal , it solved |
i change my routers like this , and everything is perfect now
|
This was likely fixed in react on master but not release yet (facebook/react#15312). In any case it's an issue with an external dependency that we will fix regardless in #16283 |
I just use material ui Menu from another package and got same issue , it strange but installing latest (similar to the spa version) react-dom solve the issue. |
i have a Drawer with default open props. when i do
props.history.push('/login')
, get this errorThe text was updated successfully, but these errors were encountered: