Auth0 Home Blog Docs

Auth0 Android Logout

Hi Team,

i implemented the new logout functionality with the latest Auth0 Android Version (1.17.0).

Now i noticed the following behavior:

  • When using the Nokia 8.1 (TA-1119) with Android 9 with the default browser app Chrome (75.0.3770.143) the logout works as intended: The internal browser loads the callback URL successfully. The same behavior is when i use Firefox (68.0) as the default browser app.
  • But when using an older Phone like HTC One M9 (Android 7) or Motorola XT1032 (Android 5.1) orSamsung Tablet SM-T520 (Android 4.4.2) the logout only works with firefox as the default browser app. With Chrome (75.0.3770.143) as the default browser app the callback does not fire back correctly. A blank browser appears ans stays open, it does not switch back into the app. This behavior is seemingly random: under the same circumstances it sometimes works and sometimes does not, I could not figure out what the cause might be.

It seems that the logout process with the Chrome as the default browser on older smartphones is not working properly and therefore does not work. Has anyone already noticed a similar behavior?

Here is the log for the HTC One M9 Firefox default browser app (it works):

2019-07-29 08:53:58.639 10449-10449/XXXapplicationIdXXX V/CallbackHelper: The Callback URI is: XXXCallbackURIXXX
2019-07-29 08:53:58.641 1315-3547/? I/ActivityManager: START u0 {flg=0x4000000 cmp=XXXapplicationIdXXX/com.auth0.android.provider.AuthenticationActivity (has extras)} from uid 10412 pid 10449 on display 0
2019-07-29 08:53:58.696 10449-10449/XXXapplicationIdXXX V/CustomTabsController: Trying to bind the service
2019-07-29 08:53:58.697 10449-10449/XXXapplicationIdXXX V/CustomTabsController: Bind request result: true
2019-07-29 08:53:58.725 10449-10449/XXXapplicationIdXXX D/CustomTabsController: CustomTabs Service connected
2019-07-29 08:53:58.726 10449-10757/dXXXapplicationIdXXX D/CustomTabsController: Launching URI. Custom Tabs available: true
2019-07-29 08:53:58.732 1315-1422/? D/InputMethodManagerService: Switching to client XXXapplicationIdXXX(10449), IME=com.htc.sense.ime/.HTCIMEService
2019-07-29 08:53:58.793 10449-10449/XXXapplicationIdXXX V/CustomTabsController: Trying to unbind the service
2019-07-29 08:53:58.960 10541-10577/? D/GeckoViewModule: queue GeckoView:LoadUri, data={"uri":XXXLogoutURIXXX,"flags":0}
.....

Here is the log for the HTC One M9 Chrome default browser app (it does not work):

2019-07-29 08:56:38.702 11221-11221/XXXapplicationIdXXX V/CallbackHelper: The Callback URI is: XXXCallbackURIXXX
2019-07-29 08:56:38.704 1315-1421/? I/ActivityManager: START u0 {flg=0x4000000 cmp=XXXapplicationIdXXX/com.auth0.android.provider.AuthenticationActivity (has extras)} from uid 10412 pid 11221 on display 0
2019-07-29 08:56:38.778 11221-11221/XXXapplicationIdXXX V/CustomTabsController: Trying to bind the service
2019-07-29 08:56:38.780 11221-11221/XXXapplicationIdXXX V/CustomTabsController: Bind request result: true
2019-07-29 08:56:38.819 11221-11221/XXXapplicationIdXXX D/CustomTabsController: CustomTabs Service connected
2019-07-29 08:56:38.823 11221-11619/XXXapplicationIdXXX D/CustomTabsController: Launching URI. Custom Tabs available: true
2019-07-29 08:56:38.849 1315-3581/? D/InputMethodManagerService: Switching to client XXXapplicationIdXXX(11221), IME=com.htc.sense.ime/.HTCIMEService
2019-07-29 08:56:38.961 11221-11221/XXXapplicationIdXXX V/CustomTabsController: Trying to unbind the service

Best Regards,
Fabian

Hi Team, any update on this issue?