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
Maximum call stack size exceeded (native stack depth) when loading from EAS Update #4921
Comments
I have the same error after upgrading to React Native 0.71. |
Same issue here |
Maybe related to expo/expo#23382 |
I also face this issue in expo prebuild unless I run ./gradlew assembleRelease in android folder it work fine if I run yarn android --variant=release is crashed |
Same for me, when using latest RN version + reanimated 3 it leads to crash with react-navigation/drawer |
This randomly started happening to me out of nowhere does anybody have a workaround? |
Update: This issue is confirmed to be fixed by upgrading to 3.6.0 |
Hi @sagihsh. Does this error still occure in your case? I tried to reproduce it, but everything works for me. If so, does it still crashes with Expo SDK 50? |
I am still having this crash with the updated version. Again, I'm not sure it comes from react-native-reanimated and my stacktrace is different. |
I had this issue as soon as I upgraded to SDK 50 as well. I was able to find the root cause for my case if that's helpful for anyone else. My issue was in I fixed this using
|
i have same when i install core-js & jwt-decode |
same here |
Description
Hi, I am running an Expo managed app with SDK 49, and Reanimated 3.3.0
After upgrading to SDK 49 (and to Reanimated 3.3.0 which goes with it), my app started crashing when loaded from an EAS update using the Expo Go app, while working fine locally (Both with Expo Go or in a development build).
While debugging the issue I noticed that it only happens while I still have some usage of reanimated. Once reanimated is out, the issue goes away.
On iOS it crashes completely, in Android in hangs on 'New update available, downloading...'
I have pulled the following errors from the iOS logs (similar error appears in Android logcat logs too):
Steps to reproduce
npm i
npm start
and see the project runs locallyeas update
command to make an update (you will probably have to change the configuration in app.json to match an Expo project you have access to, possibly a fresh one you created. See 'extra.eas.projectId' & 'updates.url' keys in app.json file)Snack or a link to a repository
https://github.com/sagihsh/expo-sdk-49-eas-update-crash-example
Reanimated version
3.3.0
React Native version
0.72.3
Platforms
Android, iOS
JavaScript runtime
Hermes
Workflow
Expo managed workflow
Architecture
Paper (Old Architecture)
Build type
None
Device
Real device
Device model
iPhone 13 for iOS / Samsung Galaxy S8 for Android
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: