RNBootSplash with react-native-auth0 not working on Android?

[VilleMiekkoja]

I have a react-native project with react-native-bootsplash. I'm using useEffect for hiding the screen like this:

const IntroScreen: React.FC<IntroScreenProps> = ({
  navigation,
}) => {
  useEffect(() => {
    RNBootSplash.isVisible().then(isVisible => {
      if (isVisible) {
        return RNBootSplash.hide({ fade: false });
      }
    });
  }, []);

  return <Text>Is this visible?</Text>;
};

The setup is so that when user arrives to this page, the splash-screen has already been hidden before in the previous page. From the previous page we move to this page, and then the splashscresn stays on (without logo, just the splashscreen background color on full screen). There's also auth0 login before we move from the previous page (that is a login page). Not sure if it affects to this. But if I comment the whole useEffect out, then there's no issue. But why do I then want to try hiding it in this page if it has already been hidden in the previous page? That is because in some cases this page might be the first page already (if user has logged in before). I could of course maybe send some kind of variable to this page that if we already know the bootsplash has been hidden, but I see no reason why the code above should not work on this situation as well. The issue only happens on android. On iOS it's working fine.

I will setup a workaround for this unless someone knows what I'm doing wrong? Is it not allowed to call isVisible() function if it has already been called once? I fear this might be some kind of timing issue. Here are the relevant library versions:

"@react-navigation/native": "^6.1.7",
"@react-navigation/native-stack": "^6.9.13",
"react-native": "0.72.3",
"react-native-bootsplash": "^5.1.3",

Android emulator: Pixel 2 API 33

[zoontek]

@VilleMiekkoja There no need to call isVisible before hide. If it's already hidden, nothing will happen and the promise will resolve.

const IntroScreen: React.FC<IntroScreenProps> = ({
  navigation,
}) => {
  useEffect(() => {
    RNBootSplash.hide({ fade: false });
  }, []);

  return <Text>Is this visible?</Text>;
};

[zoontek]

You're sure that you can't create a small repro? I can create an Auth0 project, account etc on my own, but if I don't have your code / flow I might not be able to reproduce it.

[VilleMiekkoja]

Wondering if it would be just easier to give you access rights to the repository. I fear the issue might be some kind of race condition, or memory related. Why would it otherwise make a difference what I put to the useEffect of the next screen that we move after login? I'll test if I can reproduce the error also against a cloud backend. That way running the app locally would be enough and would not need to think about how you would launch the backend part etc..

[VilleMiekkoja]

Was able to reproduce it against production backend also. I can give you read access to the repository and guide how to test this @zoontek . I have it on bitbucket. Is this your email: zoontek(at)gmail.com?

[zoontek]

Yes, this is my email 🙂

[VilleMiekkoja]

I sent you an invite.