Cannot login successfully in specific situation.

[tedhsieh17]

Hello, I have a question about the login. The user cannot log in successfully if our app is recycled by the system when opening the external browser by invoking the SDK login function. I would like to know how to handle this situation. Thanks.

Here is a video to simulate the scenario by turning on the Don't keep activities from the Developer options and the test app is from the example project attached to the VRoid SDK (Assets/VRoidSDK/Examples/CharacterModelExample/Scenes/Example.unity)

Screen_Recording_20230901-104632_Test_VRoidSDK_020.mp4

[nyamadan]

Hi. I’ll investigate the issue.

[nyamadan]

We tried to fix it, but we couldn't.

"Don't keep activities" is an emulation function for events that occur when memory is low.
We do not believe this problem occurs that often.

Could you please tell me when exactly this is a problem?

[tedhsieh17]

On some devices (ex: Pixel 3a XL), we often encounter the issue that the system recycles our app during the login process. Is there any suggestion to workaround it?

[tedhsieh17]

Hi @nyamadan , do you have any suggestion or workaround to make it login successfully? We tried to stop other apps except for our app and the browser but no luck.

[nyamadan]

In v0.5.0, the app link implementation was changed to ChromeCustomTabs.
This makes it less likely that the app will be killed.

However, if "Don't keep activities" is enabled, the program is forced to be killed...

[tedhsieh17]

Hi @nyamadan, we updated the SDK to a version higher than v0.5.0, but some users still report they cannot login successfully. It seems the system recycles and restarts our app between receiving and sending deep links to our app. Do you have any suggestion or workaround to avoid that and make it login successfully? 🙏

[gao80840]

In conclusion, there doesn't seem to be a solution.

It appears that "Activity" can be killed when memory usage becomes high. We have made adjustments to make it less likely to be killed, but this does not guarantee a resolution.

Also, it seems that Auth0.android has given up on making it compatible with the "Don't keep activities" setting.

The discussion at the URL below is helpful.
auth0/Auth0.Android#242

Since it's a specification on the OS side and there's little we can do, unfortunately, the solution will likely involve asking users to stop background apps and take other measures.