Application restarts instead of returning from authenticate()

[jordibuj]

I can't make authenticate() work consistently in my application. After a fresh start, it calls authenticate(), the browser tab appears, user logs in, and returns to the application. But it's like a fresh start of the application again, it doesn't continue after the call to authenticate() as expected. Thus it goes to the browser login screen again.

Not sure if it's related but if I launch React Native DevTools, it disconnects a few seconds after the browser tab is shown.

I ran also the examples/demo app, and I've seen it behaving like this, although sometimes it works as expected (it doesn't disconnect if devtools open, and continues after the call to authenticate() upon returning from the browser tab.

Has anyone found this behaviour, even with the demo example?

[jordibuj]

The native logs show the reason: the device is too low on memory, and Android goes on killing background apps. When my app (or the example/demo app) is put on the background while the user is at the IdP login, it takes just a few seconds until the system notices and kills the app. That's why it cold starts instead of continuing after the authenticate() call.

This has been found before #360 #743 to depend on a react-native issue which remains unsolved for years, affecting many libraries.

Has anyone found a good workaround for such a critical scenario as authenticating a user?