Samidarex
commented
7 months ago Hi @ideveloperaz, have you considered adding "launchMode: SingleTask" into your main activity? Also are you using intent-filters which will handle the callback from the custom chrome tabs?
If not here's an example of an intent filter that might help you:
[IntentFilter( new[] { Intent.ActionView }, Categories = new[] { Intent.CategoryDefault, Intent.CategoryBrowsable }, DataScheme = "https", // Replace with your actual scheme DataHost = "test.com" // Replace with your actual host )];
I hope this proves helpful in resolving your issue.
ideveloperaz
Hello,
We have OAuth and use WebAuthenticator to help us get web access token from custom ID Server if doing login and logout in app like normally then everything ok and WebAuthenticator opens browser in app ... but when we login then close(kill) app, then open app again do logout - we could see external chrome is opening and could redirect back to app, but when we do login then WebAuthenticator also opens external chrome and I see that app proceed after WebAuthenticator.AuthenticateAsync() BUT opened external chrome is not closed and does not open app ... it just stays on that Chrome login page, but app in background continue working as expected after WebAuthenticator.AuthenticateAsync()
this happens only for Android
Steps to Reproduce
pls see in description
Expected Behavior
could open back app after login, during that special user case scenario
Actual Behavior
could not open app back and stays on external Chrome browser login page (though app in background proceeds like expected)
Basic Information