Android system browser
Starting with MSAL.NET 2.4.0-preview, MSAL.NET supports browsers other than Chrome and no longer requires Chrome be installed on the Android device for authentication.
It is recommended to use browsers which support custom tabs, such as the following browsers:
|Browsers with custom tabs support||Package Name|
In addition to browsers with custom tabs support, based on our testing, a few browsers that do not support custom tabs will also work for authentication, such as Opera, Opera Mini, InBrowser, and Maxthon. See table for test results.
If the user has no browser enabled on the device, MSAL.NET will throw an
- Mitigation: You need to inform the user that they should enable a browser (preferably one with custom tabs support) on their device.
If authentication fails (ex. authentication launches with DuckDuckGo), MSAL.NET will return an
- Root Problem: A browser with custom tabs support was not enabled on the device. Authentication launched with an alternate browser, which was not able to complete authentication.
- Mitigation: You need to inform the user that they should install a browser (preferably one with custom tab support) on their device.
Devices and browsers tested
|Huawei/One+||DuckDuckGo||User cancelled auth|
|Huawei/One+||UC Browser||User cancelled auth|
|One+||Dolphin||User cancelled auth|
|One+||CM browser||User cancelled auth|
|Huawei/One+||none installed||AndroidActivityNotFound ex|
Supports Custom Tabs*
See this guide with code snippets and additional information on using system browser with Xamarin Android.