[Bug] Cannot use Custom Tabs with Android 29+

[trwalke]

Logs and Network traces
Without logs or traces, it is unlikely that the team can investigate your issue. Capturing logs and network traces is described at https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/logging

Which Version of MSAL are you using ?
MSAL 4.24.0 +

Platform
xamarin android

What authentication flow has the issue?

• Desktop / Mobile
  • Interactive
  • Integrated Windows Auth
  • Username Password
  • Device code flow (browserless)
• Web App
  • Authorization code
  • OBO
• Daemon App
  • Service to Service calls

Repro
Ensure the app is targeting android 10 (API 29) in the project properties.
Ensure that the system browser is enabled in MSAL.NET (Should be on by default)
Try to acquire a token interactively

Expected behavior
MSAL should launch the custom tab browser for authentication

Actual behavior
The system browser is launched without custom tabs.

Possible Solution
Try modifying the browser tab packages that are used in the interactive auth.

microsoft-authentication-library-for-dotnet/src/client/Microsoft.Identity.Client/Platforms/Android/SystemWebview/AuthenticationActivity.cs

Lines 37 to 45 in d451b16

	// this is used to check if anything can open custom tabs.
	// Must use the classic support. Leaving the reference AndroidX intent
	#if __ANDROID_29__
	private readonly string _customTabsServiceAction =
	"androidx.browser.customtabs.action.CustomTabsService";
	#else
	private readonly string _customTabsServiceAction =
	"android.support.customtabs.action.CustomTabsService";
	#endif

[jmprieur]

@trwalke. is it a duplicate of #2139 ?

[bgavrilMS]

Closing as duplicate of #2139

[trwalke]

Not a duplicate. this is the second issue identified in #2139

[trwalke]

@tipa it appears that there is a new way to implement the custom tabs in android 29. Ive been playing around with it to see if there is a way to adapt our code with it to make it work. I managed to get the custom tab to show up but the responses do not return to our code at the moment. I was also able to get the legacy support for custom tabs to work so I think it will be ok for us to use that for now.

[tipa]

Not sure what you mean with legacy support buty ou can test the file attached if you need it. I am using it successfully to authenticate to many services, like Dropbox, Google Drive etc.
AuthorizationManagementActivity.zip

You can start the auth flow with AuthorizationManagementActivity.AuthenticateAsync(url); and the WebAuthenticationCallbackActivity will be called if the scheme is set correctly.

[trwalke]

@tipa I was referring to using
"android.support.customtabs.action.CustomTabsService"

as opposed to
"androidx.browser.customtabs.action.CustomTabsService".

which would require us to use the custom tab intent here
https://developer.android.com/reference/androidx/browser/customtabs/CustomTabsIntent

this appears to be the way to implement customtabs in android 29+

Perhaps legacy is the wrong word.

I am able to get the custom tabs working again with "android.support.customtabs.action.CustomTabsService" however so we can release a fix with that

[tipa]

Yay, looks fixed with 4.29.0 - thanks!

[bgavrilMS]

Thank you for patience @tipa !