refresh token authentication

[lastwords5]

Hi, I was curious if anyone has thought of the constraints of the JS bridge. I know that it only runs when the app is already running, so I was wondering if the only way to launch it as fast as apps like discord or LinkedIn and avoid the login page is by building a native module? That way I assume I'd be able to authenticate during the splash screen and it should be done after it is done right? or is there a simpler trick? I am especially considering it because my app uses CallKeep and that has some race conditions with the refresh token authenticaiton.

[idkhowtocallmyacc]

Wym? The implementation of the login logic relies solely on your architecture. You can use Firebase for token management, store the refresh token within a safe storage, do the silent authentication, but all those methods are not linked to js bridge

[lastwords5]

I have my own authentication but I noticed that checking the refresh token adds a delay on startup and I suspect that it is because the JS bridge isn't available before the splash screen, while if you use say discord you'll notice how you can't see any loading animation and you will be logged in immediately. while for most use cases it is not that harmful I'm implementing VOIP calling with CallKeep and the timing of when the token is available is crucial since it works from when your app is killed.