My current Android Application uses
Chrome Custom Tabs to both Sign In & Out.
The longer our users are signed in the greater the chance that user Sign Out fails.
e.g. when the user has ben signed in for 60+ mins the Sign Out consistently fails
Having employed an HTTP proxy we have discovered that all the user identifying cookies are not attached to the Sign Out call.
I was under the impression that Chrome dealt with all cookies and user applications do not have authority to affect them.
How are we losing the cookies for user sessions over 60 minutes?
Is this a known issue with Chrome Custom Tabs?