Open alaughlin opened 6 months ago
same issue... someone knows how this happened?
I don't know why, but I had some problems with react-native-reanimated: 2.7.1
when I installed in a simple project with some drawer navigation that uses expo: 50.0.8
and react-native: 0.73.4
A solution that I found was to downgrade it to 3.6.2 and keep react-native-gesture-handler
to 2.14.0.
I don't know why, but I had some problems with
react-native-reanimated: 2.7.1
when I installed in a simple project with some drawer navigation that usesexpo: 50.0.8
andreact-native: 0.73.4
A solution that I found was to downgrade it to 3.6.2 and keep
react-native-gesture-handler
to 2.14.0.
~so at reanimated 3.6.2 and react-native-gesture-handler 2.14.0, I'm no longer getting crashes, however the shared element is not animating~
I spoke too soon. I restarted the app in the simulator and it's back to crashing again.
No sé por qué, pero tuve algunos problemas
react-native-reanimated: 2.7.1
cuando instalé en un proyecto simple con un cajón de navegación que usaexpo: 50.0.8
yreact-native: 0.73.4
Una solución que encontré fue degradarla a 3.6.2 y mantenerlareact-native-gesture-handler
en 2.14.0.~entonces, en reanimated 3.6.2 y react-native-gesture-handler 2.14.0, ya no tengo fallas, sin embargo, el elemento compartido no se anima~
Hablé demasiado pronto. Reinicié la aplicación en el simulador y volvió a fallar.
Diste con la solucion?
I just tested spinning up a barebones react-native/expo app and while shared element transitions are not crashing, they also just aren't working at all.
I think something is just overall broken with reanimated 3.6/3.7 and react-native 0.73
same issue.
It's not crashing but ... I've got here a really weird behaviour indeed! react-native-reanimated: "~3.6.2"
https://snack.expo.dev/@tmaszko/sharedtransitiontest
im using version 3.6.2 and gesture in 2.14.0 because is the versions recommended by expo, but, not working too. The same behavior of @TMaszko example.
I've created an issue in the expo repo with a more robust explanation here :) https://github.com/expo/expo/issues/27606#issuecomment-1992715260
FWIW in Expo Go it just doesn't work, but in development builds it outright crashes the app for me
I have the same crash logs from ios
Experiencing the same issues with Expo 50.0.14, Reanimated 3.6.2, and React Native 0.73.6. Spent roughly 12 hours trying various workarounds to no avail.
Also am on Expo 50 and am having the same issue. Since upgrading, the transition does not work but we needed to upgrade for compliance and now have dependencies on it...
I can confirm that upgrading from 3.8.1 to 3.9.0 results in this issue. Downgrading resolves the issue.
@anon-r-7 strangely, I have this issue on 3.3.0
Description
We've recently upgraded our Expo app from SDK 49 to 50, including upgrading
react-native-reanimated
from 3.3.x to 3.7.x. We also upgradedreact-native
from 0.72 to 0.73. Now anytime we navigate between screens that share an element, the entire app (not just React) crashes.I've attempted to downgrade
react-native-reanimated
back to 3.3.x, but the app will no longer build with that older version, with Fastlane throwing errors aboutYoga.h
not being found. I'm guessing the older version of this library is no longer compatible with the more recent versions of expo and/or react-native?I am unable to reproduce this issue with a new Expo app. Our app is large and it's not possible to share the repo. It's possible one of the deps inside package.json is causing issues? I am going to paste the beginning of the crash report here showing the thread running reanimated is the one that crashes (it's from the iOS simulator, but it also happens on real hardware), as well as the contents of our package.json. Please let me know if there's anything else I can provide to help debug this.
package.json deps:
Crash report:
Steps to reproduce
<Animated.View>
that share the samesharedTransitionTag
propSnack or a link to a repository
N/A
Reanimated version
3.7.1
React Native version
0.73.4
Platforms
iOS
JavaScript runtime
None
Workflow
Expo Dev Client
Architecture
None
Build type
None
Device
None
Device model
No response
Acknowledgements
Yes