Browser with custom tabs support not found.

[lolucosmin]

Describe the bug
Hello, I am using aws mobile client on android and after I update from 2.26.0 to last version 2.30.0, on some devices
I am getting this exception "Browser with custom tabs support not found." from AuthClient.
When I did update I followed the documentation from here for the correct version "Version 2.27.0 and above":
https://docs.amplify.aws/sdk/auth/hosted-ui/q/platform/android/#automated-setup-with-cli

To Reproduce
A code sample or steps:

This issue can be reproduced in this way:
1. Disable the Chrome browser.
2. Try sign in and you will get this exception: new BrowserNotInstalledException("No browsers installed.").
3. Close app, then enable Chrome browser.
4. Open the app and try again the sign in. Now the browser check passed but checking for custom tab support failed:
new CustomTabsNotSupportedException("Browser with custom tabs support not found.")

The issue is on this class: com.amazonaws.mobileconnectors.cognitoauth.AuthClient on this function:
    private void launchCustomTabs(final Uri uri, final Activity activity, final String browserPackage) {
    	try {
            if(!isBrowserInstalled()) {
                userHandler.onFailure(new BrowserNotInstalledException("No browsers installed."));
                return;
            }
            if(!isCustomTabSupported()) {
                userHandler.onFailure(new CustomTabsNotSupportedException("Browser with custom tabs support not found."));
                return;
            }
            CustomTabsIntent.Builder builder = new CustomTabsIntent.Builder(mCustomTabsSession);
            mCustomTabsIntent = builder.build();
            if(pool.getCustomTabExtras() != null)
                mCustomTabsIntent.intent.putExtras(pool.getCustomTabExtras());
            if(browserPackage != null) {
                mCustomTabsIntent.intent.setPackage(browserPackage);
            }
            mCustomTabsIntent.intent.setData(uri);
            if (activity != null) {
                activity.startActivityForResult(
                    CustomTabsManagerActivity.createStartIntent(context, mCustomTabsIntent.intent),
                    CUSTOM_TABS_ACTIVITY_CODE
                );
            } else {
                Intent startIntent = CustomTabsManagerActivity.createStartIntent(context, mCustomTabsIntent.intent);
                startIntent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_NO_HISTORY);
                context.startActivity(startIntent);
            }
    	} catch (final Exception e) {
            userHandler.onFailure(e);
        }
    }

Which AWS service(s) are affected?
aws-android-sdk-cognitoauth

Environment Information (please complete the following information):

• AWS Android SDK Version: 2.30.0
• Device: Mi 10T Pro, Redmi K20, Redmi Note 7, Mi 9T Pro, Redmi Note 8T, Mi 10T Lite, HONOR 10i, realme 6, POCO X3 NFC, Galaxy S20, Redmi 9T, Redmi Note 8 Pro
• Android Version: Android 9, Android 10, Android 11
• Specific to simulators: No

Additional context
I tested a lot of devices and on some devices is working very well.
Also to be sure is version 2.30.0 the problem I downgrade the version to 2.26.0 and the issue was gone.

[rahul-insight]

I'm observing the same issue on Samsung Galaxy S10 with a Flutter App

I recently started getting the below error when calling Amplify.Auth.signInWithWebUI from my Flutter App

amplify:flutter:auth_cognito: AuthException AuthException{message=Sign-in with web UI failed, cause=com.amazonaws.mobileconnectors.cognitoauth.exceptions.CustomTabsNotSupportedException: Browser with custom tabs support not found

The Amplify packages I'm using are:

amplify_auth_cognito: ^0.2.0
amplify_api: ^0.2.0
amplify_flutter: ^0.2.0
amplify_core: ^0.2.0
amplify_analytics_pinpoint: ^0.2.0

The issue only started happening for Android (device only, not on emulator). Does anyone know what might suddenly be causing this issue on the Android device and how to resolve it?

The build command I'm using is:
flutter build appbundle --release

[lolucosmin]

So I did more tests and I have no idea why that function isCustomTabSupported() is not working well after I install or after I enabled the browser.

Before do this things be sure you have 1 browser(in my case Chrome) installed is more clear hot to test.
Case:

1. Disable or uninstall the Chrome browser.
2. Try sign in and you will get this exception: new BrowserNotInstalledException("No browsers installed.").
3. Close or destroy the app.
4. Enable or install the Chrome browser.
5. Open the app and try again the sign in. Now the browser check passed but checking for custom tabs support failed:
   new CustomTabsNotSupportedException("Browser with custom tabs support not found.").

So what I did, I got the code from SDK(com.amazonaws.mobileconnectors.cognitoauth.AuthClien) which is checking for custom tabs support and I put it in app level before pressing the sign in button.
In app level: isCustomTabSupported() return me true and in SDK isCustomTabSupported() return false.
Does anyone have any idea why this is happening?
@rjuliano @raphkim

[raphkim]

Thank you for reporting this. It is possible that the logic inside SDK is unable to fully access app's data to be able to properly determine whether the device supports custom tabs browser or not, which would explain why you are observing different results depending on whether you add the check in the app or not.

It was meant to be a first-level of defense against an attempt to use the hosted UI with an insecure browser, but I can see how a false-negative can cause inconvenience. I will pass this along to the team to further investigate an alternative solution.

[div5yesh]

@lolucosmin Can you please share your AndroidManifest.xml?

[div5yesh]

For android 9 or above, to query for custom tabs it required to add queries section to AndroidManifest. Please refer: https://docs.amplify.aws/lib/auth/social_signin_web_ui/q/platform/android/#update-androidmanifestxml and let us know if this resolves your issue.

[lolucosmin]

@div5yesh Hi, I can share a part of it, I have that part with queries.

<uses-feature
    android:name="android.hardware.camera.autofocus"
    android:required="false" />

<uses-feature
    android:name="android.hardware.telephony"
    android:required="false" />

<uses-feature
    android:glEsVersion="0x00020000"
    android:required="true" />

<queries>
    <package android:name="com.linkedin.android" />
    <package android:name="com.facebook.katana" />
    <package android:name="com.google.android.apps.chrome" />
    <package android:name="com.android.chrome" />
    <package android:name="com.chrome.beta" />
    <package android:name="com.chrome.dev" />

    <intent>
        <action android:name="android.intent.action.VIEW" />
        <data android:scheme="https" />
    </intent>

    <intent>
        <action android:name="android.intent.action.VIEW" />
        <data android:scheme="http" />
    </intent>

    <intent>
        <action android:name="android.support.customtabs.action.CustomTabsService" />
    </intent>

</queries>

<application
    android:name=".BFanLabelApplication"
    android:allowBackup="false"
    android:hardwareAccelerated="true"
    android:icon="@mipmap/ic_launcher"
    android:label="@string/app_name"
    android:networkSecurityConfig="@xml/network_security_config"
    android:preserveLegacyExternalStorage="true"
    android:requestLegacyExternalStorage="true"
    android:supportsRtl="true"
    android:theme="@style/AppTheme"
    tools:ignore="GoogleAppIndexingWarning,UnusedAttribute"
    tools:replace="android:allowBackup">

    <uses-library
        android:name="org.apache.http.legacy"
        android:required="false" />

    <uses-library
        android:name="android.test.runner"
        android:required="false" />

    <uses-library
        android:name="android.test.base"
        android:required="false" />

    <uses-library
        android:name="android.test.mock"
        android:required="false" />

.......................................

    <activity
        android:name="com.amazonaws.mobile.client.activities.HostedUIRedirectActivity"
        android:exported="true">
        <intent-filter>
            <action android:name="android.intent.action.VIEW" />

            <category android:name="android.intent.category.DEFAULT" />
            <category android:name="android.intent.category.BROWSABLE" />

            <data
                android:host="${sign_in_host}"
                android:scheme="${sign_in_scheme}" />

            <data
                android:host="${sign_out_host}"
                android:scheme="${sign_out_scheme}" />

        </intent

[AndreasBoehm]

I created a pull-request to address that issue: #2721

[lolucosmin]

Hi, any news related to this issue? Still is there on 2.36.0. I will wait the #2721 to see if after will works. @AndreasBoehm to reproduce my issue please follow my steps from above.

[eeatonaws]

A PR to fix the issue has been included in version 2.37.1.