-
Notifications
You must be signed in to change notification settings - Fork 739
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
[BUG] React 18 issues #1421
Comments
Thanks for the report! With layoutId, are the other issues specifically in relation to AnimatePresence? |
All issues I've noticed are related to |
Ah yeah that makes sense it still isn't concurrent safe, we'll have to take a look at this soon. |
That would be awesome, thanks @mattgperry. This is blocking our upgrade to React 18 and we love Framer Motion :) |
Any updates on this? I'm also dealing with this issue |
Also facing this issue when upgrading to react 18. Since this is Open for such a long time, what can we do to get more focus on fixing things for react 18? I can provide a reproduction codesandbox if that helps. But it's also stopping me from upgrading to react 18, therefore it would be great to see at least a workaround for this. |
We've been on 18 for a while so please make new tickets with Sandbox examples of any issues you run into. |
Using React 18 a component inside
<AnimatePresence/>
does not unmount from the DOM after the exit animation finishes. There are also other issues involvinglayoutId
, but the one that seems really broken is the<AnimatePresence/>
.It seems that most issues are related to the strict mode. Disabling it fix the issue.
Framer version: 5.5.5
React version: 18.0.0-rc0
The text was updated successfully, but these errors were encountered: