-
Notifications
You must be signed in to change notification settings - Fork 194
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
Add support for React Navigation 4 #215
Comments
Yes please |
Hey, can we help with this? What's different? I haven't upgraded yet, but I might if there's some pointers for this. |
Should probably be targeting React Navigation 5 instead, as it is a complete rewrite |
We're finishing of the next version of Fluid Transitions and will be targeting React Navigation 5.0 for shared element transitions! |
@chrfalch great news! Is there any public repo or branch that we can already contribute to or use? |
so any all we need to migrate react navigation to 3 v? |
probably disappear transition does not work because of 4v |
I am using it with v4 but shared transition do not works, it show's blank. Appears and disappers works well. |
@humbertocruz nobody ever said that it works with v4, i’m not quite sure what you expected |
@chrfalch what's the status on the release? excited :) |
What would need to be patched to work under v4? Currently decided to downgrade to v3 to get this to work... there's no warnings or anything to try to fix. |
v5 react-navigation is avaiable, so excited. Wating for fluildNavigation update. |
Hi @chrfalch |
Any updates? |
The last commit was in June 2019, this lib died? D: |
I guess so... I haven't seen much activity, so if you need something like this with newer versions you'll need to work it out yourself 😕 I haven't had the need or the time for this one, so haven't looked into it. |
See my answer at xotahal/react-native-motion#6 (comment) |
you can try this library -> https://github.com/IjzerenHein/react-navigation-shared-element working good on rn-navigation v5 |
No description provided.
The text was updated successfully, but these errors were encountered: