Interactions briefly unresponsive after navigating between screens

Our team has been doing some experimentation with useScreens in react-navigation. One thing I noticed was the time it takes for a screen to respond to touch events seems longer with react-native-screens enabled. Purely anecdotal, but trying to nav back and forth between screens pretty consistently takes 1 extra quick tap with useScreens compared to not using it.

Seeking feedback if this could be react-native-screens specific, the implementation in react-navigation, or possibly something in our own app.

[WoLewicki]

@Hirbod so does it only happen in modals, or in all presentation kinds? Also, could you somehow show the difference in the time of the ability to click, scroll in the next/previous screen when native-stack compared to e.g. Settings app and App Store app (there is a modal there when you click your profile icon). I can spot the delay in those apps too, but probably I am missing something. Also, when providing stackAnimation: 'none', you can click the buttons immediately, which would suggest that there is no delay introduced by us. But here too, I might be missing something.

[bartzy]

@WoLewicki By using import { createStackNavigator } from 'react-navigation/stack' and also calling enableScreens, are we even getting the native navigation behavior at all? I don’t quite get what’s the behavior with the regular createStackNavigator and enableScreens. I thought this library makes sense only with import { createNativeStackNavigator } from 'react-native-screens/native-stack'.

Also, the behavior with createNativeStackNavigator is not the same in iOS as regular native apps. With a regular native app, there is no delay at all for interacting with a new view controller that was just pushed to the navigation stack. With react-native-screens + createNativeStackNavigator (+ enableScreens obivously), there’s a slight delay (probably 100-500ms?) where you can’t tap on new elements after the transition ended. That is the issue that I think most people in this thread are reporting.