Android release build hanging for approx. 10 secs on low end devices

[ahmedjamshed]

What's going on?

Android release build hanging for approximately 8 seconds at the start on low-end devices like Xiaomi Mi A2 Lite (Redmi 6 Pro)

Steps to reproduce:

Just create new boilerplate and release the build on android and on starting the app, interact with notification bar or something else. I believe this is the issue in some configuration of react-navigation.

[viralS-tuanlv]

the same issue on some device, the reason is this project is using react-native-screens/native-stack, i have move to @react-navigation/stack and the issue gone

[sheng-di]

the same issue on some device, the reason is this project is using react-native-screens/native-stack, i have move to @react-navigation/stack and the issue gone

Yeah, I wonder why bowser choose to use react-native-screens. Does it make the navigation faster?

[rdewolff]

Are you talking about the first white screen you get on first load on Android device?

[nishithtatva]

Are you talking about the first white screen you get on first load on Android device?

Yes. There seems to be issue for only low end devices.

[AfrazHussain]

Firstly, would like to express my deepest gratitude to the creators of this boilerplate. Can't thank them enough.

I can verify that this problem exists on low-end Android devices. There is a significant lag on startup. For now you can try out this solution, i.e. use Platform.select(): #330 (comment)

That said, I was wondering why the team switch from createStackNavigator to createNativeStackNavigator in the first place, in this PR: https://github.com/infinitered/ignite-bowser/pull/311/files#diff-bfc519320393aebaf127a89c9c59ea33. I've previously had a lot of issues with native stack navigator which is why I've stuck with createStackNavigator