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
Known issue: Expo Router / React Navigation crash in SDK 51 when switching tabs (clearSharedTransitionConfigForTag crash) #28618
Comments
Hey @marklawlor, thanks for reporting this issue. This one was tricky to reproduce as it happens only if I've submitted a proper fix to Reanimated repository: The PR is already merged. It will be available in today's nightly release as well as published in next stable release (3.11.0). We're sorry for inconvenience. Any chance this change will make it into SDK 51? 🙏 |
Development clients & production buildsPlease upgrade your version of Expo GoWe will need to publish a new version of Expo Go. In the meantime, please switch to using a custom development client. |
for the record, also saw this crash when using an Expo Go + React Navigation app that
this App was started from the TypeScript template (SDK 51) and then added React Navigation. as mentioned above npx expo install react-native-reanimated (installs and adding import 'react-native-reanimated'; to the root |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Using what @jpdriver said I was able to fix my react-navigation/native-stack navigation from going in-between screens and the
Then I just imported the library to my App.tsx file using:
This worked for me and I didn't have to do anything else. This is a really strange issue. |
I've updated the issue description to include instructions for non-Expo Router projects. Important If the instructions in the first post do not fix your issue, please create a new issue. You may be experiencing a different issue - but we cannot tell / help unless its reported properly |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
If you're using Expo prebuild, please upgrade to Reanimated 3.10.1:
If you're using Expo Go, please apply the workaround: import 'react-native-reanimated'; |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Important If the instructions in the first post do not fix your issue, please create a new issue. You may be experiencing a different issue - but we cannot tell / help unless its reported properly Please do not ask for support for other issues - your comment will be hidden as off-topic. Please follow the correct procedure and create a new issue |
This comment was marked as off-topic.
This comment was marked as off-topic.
I did this but still my app crashes on real device is there any other known issues with this package or should I look into other packages if they are the reason? I’m not getting any error just when I boot my app on Expo Go on my phone it downloads data and when it’s time to boot up it crashes and expo closes. |
Using version 3.11.0 of react-native-reanimated keeps giving me the following error:
I had to revert to 3.10.1 to avoid this error. |
I'm seeing the same issue with using react navigation with expo 51. i've attempted every suggested work around in this thread but nothing works. In addition I ran a development build, but see the same results of the app freezing and installed expo version 51.0.4. Here's my pacakage.json config
|
+1, need to do company work, do we have an eta on fix? |
I upgraded my project to SDK 51, and that's when the troubles began with the app's launch on iOS devices when i was using react navigation. This issue only occurred me on iOS, but I managed to solve it with the help of this guide. Works fine on other operating systems. |
Can you walk through the exact steps you took to solve the issue? |
Of course, the steps is on the order that give us the user, my explanation is this: 1. Create a layout route Create a layout route for a directory, for this create a file named _layout.js in the directory.
2. Install react-native-reanimated
3 Add this line on the code of the layout that previously created: import 'react-native-reanimated' Should see like this:
4 In the archive named App.js on your project add this line
That's all 👌 |
An updated version of Expo Go is now available on the App Store, version 2.31.5. This includes react-native-reanimated@3.10.1 with the fix for this issue! |
@brentvatne after the update Expo Go on iOS crashes for me after the bundle is built and before the app starts (this app worked before the Expo Go update (but crashed on navigation)). I also tried reinstalling Expo Go completely but it hasn't helped. |
@brentvatne that did not work.. still crashes on navigation |
@xixixao @graniteroad - then those may be different issues. please create a new issue with a minimal reproducible example |
The same thing, I've tried everything said and I also updated my dependencies, everything works well in Expo Go but the Android app crashes whenever I try to access pages using @react-navigation/material-top-tabs import "expo-dev-client";
import Navigation from "./navigation";
import "react-native-reanimated"
const App = () => {
return <Navigation />;
};
export default App; |
not working, when i want navigate on the screen that contains a navigation to a modal react-navigation on device physical ios and simulator iOS, please patch it |
hey folks, i'm locking this thread because the problem that we originally created this issue for is resolved as far as we can reproduce. if you are encountering crashes related to navigation, then please create a new issue with a minimal reproducible example as per the issue report template. thank you! |
Tip
This issue is now resolved. Please update to the latest version of the Expo SDK 51 /
react-native-reanimated
/react-navigation
. You will also need to update your Expo Go (either from the App store or having the CLI update your simulator) or rebuild or development client.Caution
If you are still having issues after upgrade & updating your app, please create a new issue.
An updated version of Expo Go is now available on the App Store, version 2.31.5. This includes react-native-reanimated@3.10.1 with the fix for this issue!
Previous issue description
Due to an upstream issue with `react-native-screens` (the library which powers Expo Router and React Navigation), Expo Router projects upgrading to SDK51 may experience an issue where the app quits unexceptionally when navigating between screens on iOS.We are aware of this issue and are working with Software Mansion with a fix. Unfortunately, a solution could not be deployed prior to the initial SDK51 release, but you can resolve the issue with a simple workaround.
Issue Identification
After upgrading to SDK51, your Expo Router app may crashes on iOS. This affects all Expo Go, Custom Development Clients and Production builds. When running your app in development you will receive the "Expo Go quit unexpectedly" error dialog. Clicking "report" will show the crashlog where you should see this line in the stack-trace
Expo Router Workaround
The workaround is to import
react-native-reanimated
in a top-level_layout
file.1. Create a top level
_layout
file (if you don't have one yet).You will need a top-level
_layout
file. If you don't have one already, you can use this as a template.2. Install
react-native-reanimated
Run
npx expo install react-native-reanimated
to installreact-native-reanimated
3. Import
react-native-reanimated
Import
react-native-reanimated
in the root_layout
import { Slot } from 'expo-router'; + import 'react-native-reanimated' export default function HomeLayout() { return <Slot />; }
React Navigation Workaround
Is you are using just React Navigation, please upgrade to
react-native-reanimated@3.11.0
. If you are still experiencing the issue addreact-native-reanimated
to yourApp.js
The text was updated successfully, but these errors were encountered: