Recently I had to start up a project from scratch and I had to make a general flow of splash screens, tutorial screens and authentication screens...
For further actions, you may consider blocking this person and/or reporting abuse
You could have implemented a SwitchNavigator instead of the custom resetAction function, I think. The SwitchNavigator resets the screen whenever they are unmounted and disallows going back, even with the hardware button on Android. A good tutorial is provided in the react-navigator docs: reactnavigation.org/docs/en/auth-f...
Thanks a lot Peter!
Why do you use an aditional screen (StartingScreen) instead of doing the verification on SplashScreen? And why an unecessary 4 seconds delay?
That way user always needs to wait 4 seconds for app to load, i think thats a lot of time and i would uninstall the app just because that long waiting.
You are right. I will change it :) Thanks!
Did you compile a production build of your app and then did have any white screen before the actual splashscreen appears.
Got this issue. I'm using a native SplashScreen and then this guide reactnavigation.org/docs/en/auth-f... but in between screens i get a white screen. I think my render in the "AuthLoadingPage" is taking to long to start working
I did not face this issue in production build