GestureHandler already initialized for root view

[ethantran]

I will occasionally get this error, but I am not sure how to reproduce it. All I know is that it is related to the stack navigator and how it implements react native gesture handler. When I switch it to another navigator like bottom tab, it does not throw error. I can only prevent the error temporarily by closing the app and opening it back up.

Platform: Android

"react": "16.8.3",
"react-native": "0.59.5",
"react-native-gesture-handler": "^1.2.1",
"react-navigation": "3.9.1"

const MainNavigator = createBottomTabNavigator({
  Home: {
    screen: HomeScreen
  }
});
export const AppContainer = createAppContainer(MainNavigator);

[satya164]

Closing due to no repro. If this still occurs with the latest versions, please open a new issue with a repro.

[AilsonFreire]

I am having the same problem. I don´t know why.

[Nagibaba]

I restarted Metro Bundler. Error gone

[SwordElucidator]

Any update?

[mikebouwmans]

I have this error aswell at random times. Cant seem te reproduce it manually.

[angel-luis]

Same here, after restart Expo the error gone. I didn't touch the code.

Just developing a starter project with latest RN and RNN@next.

[web-2017]

just restart your app on device, Metro Bundler, error should gone

[grantgeorge]

We're getting this crash in production builds. Open to suggestions on how to debug this in that env

[danmaas]

@grantgeorge I too have been fighting this in production. It's been affecting ~1% of sessions among my Android users on recent production builds.

I am not 100% sure, but my investigation so far points to a possible bad interaction between react-native-gesture-handler and the default behavior of the Android hardware back button in React Native (which destroys the app's MainActivity, while leaving much of the Java and JavaScript context intact, and results in a second instance of MainActivity spawning when the app is brought to the foreground again). I have noticed several bugs in various React Native libraries where the root cause lies in code that does not handle this scenario properly, and I suspect that might be the case here too.

I am currently testing this possible fix, which prevents the app's MainActivity from being destroyed and re-created as often: https://stackoverflow.com/a/60360452
(though I'm using launchMode="singleTask", not "singleTop")

My suspicion is that something goes haywire in terms of the MainActivity lifecycle and the UI elements it manages, maybe due to incomplete handling of onHostDestroy()/onHostResume(), or a race condition between JavaScript and native Java code.

Note, I am still on react-navigation 3.13, so I'm not 100% sure this applies to more recent versions. I have a pretty heavy-duty navigation setup with many nested tabs, stacks, and switches, so I'm probably stressing the react-navigation code too.

[grantgeorge]

@danmaas thanks for sharing that. Glad I'm not alone!

If it's helpful, I've found that this crash and similarly related crashes to gesture handler and/or react-navigation occur after a user has downloaded a CodePush update and the sync at least started. That's about as far as I've gotten with this and I'm doing some more digging later.

From your example, my hypothesis is that users are downloading & syncing the CodePush update which shows a white screen and trying to exit that flow by clicking hardware back.