AuthException/CustomTabsNotSupportedException when default browser does not support custom tabs

[andiigtayma]

We're using Amplify Auth with Google as the provider.
It has been working just fine for all our users however, for one it fails and logs in this message:
AuthException(message: Sign-in with web UI failed, recoverySuggestion: See attached exception for more details, underlyingException: com.amazonaws.mobileconnectors.cognitoauth.exceptions.CustomTabsNotSupportedException: Browser with custom tabs support not found.)

Device: Oppo, Android 11

So far, we've tried to modify the manifest to support this device with this:

<queries>
        <intent>
          <action android:name="android.intent.action.VIEW" />
          <category android:name="android.intent.category.BROWSABLE" />
          <data android:scheme="https" />
        </intent>
        <intent>
            <action android:name=
                "android.support.customtabs.action.CustomTabsService" />
        </intent>
 </queries>

Other things we've tried:

1. Cleared chrome browser cache
2. Updated browser to latest version

Using Plugins:

  amplify_auth_cognito: ^0.2.2
  amplify_flutter: ^0.2.2
  google_sign_in: ^5.0.7

[ragingsquirrel3]

@andiigtayma there is some discussion of similar issue on #863 which points to aws-amplify/amplify-android#678 (comment) so you can see if the installed browsers support custom tabs.

[Jordan-Nelson]

@andiigtayma - Just to confirm, the device has Chrome installed? Can you check what browser is set as the default on the device (listed in settings)?

[andiigtayma]

@Jordan-Nelson this worked!
Set the browser to default and the user was able to login.

[Jordan-Nelson]

Okay. I am actually going to re-open this and mark it as a bug. We should be able to handle the case when a supported browser is installed, but not set to the default.

Do you know what browser was set as the default when it was not working?

[andiigtayma]

@Jordan-Nelson We had no idea about how the user may have set up their phone.

Before the issue was reported to us, we looked into the logs and found
AuthException(message: Sign-in with web UI failed, recoverySuggestion: See attached exception for more details, underlyingException: com.amazonaws.mobileconnectors.cognitoauth.exceptions.BrowserNotInstalledException: No browsers installed.

The user confirmed that they had Google Chrome installed and we asked them to clear cache/ update.

Then we added the https intent query into the manifest and gave the user a new build. This changed the error to AuthException(message: Sign-in with web UI failed, recoverySuggestion: See attached exception for more details, underlyingException: com.amazonaws.mobileconnectors.cognitoauth.exceptions.CustomTabsNotSupportedException: Browser with custom tabs support not found.)

[dnys1]

Hi @andiigtayma, I noticed you may be on older versions of the Amplify Flutter libraries. There have been significant improvements made recently, and I wonder if you'd willing to try out the latest version (^0.6.0) to see if the issue still persists.

[andiigtayma]

Hello @dnys1, I have a Samsung with Android 12. The default browser is Chrome, and since the issue was due to not having a default browser setup, I tried this:

1. if I disable Chrome and debug the app, I get:
   AuthException(message: Failed to sign out, recoverySuggestion: See attached exception for more details, underlyingException: com.amazonaws.mobileconnectors.cognitoauth.exceptions.AuthServiceException: Timed out while waiting for sign-out redirect response.)

2. If I download a different browser, it automatically switches default system browser to the available option.

So, I don't think I would be able to test this unless I know a way to have Chrome on device and not have a default browser.
Oh and I did try this with updated amplify plugins.

[dnys1]

In both of those cases, that is the correct behavior, though. If you disable Chrome and have no other browsers, the request should fail. And if you have installed other browsers and made those default, that is what will be chosen.

You say you added the queries intent filter only after your user experienced the CustomTabsNotSupportedException? This is required as of Android 11 and could alone be the cause of the exception. Has your user been able to reproduce the issue since adding that filter and upgrading the Amplify libraries?

[Jordan-Nelson]

For anyone facing this issue, this has been addressed in the latest dev-preview release of Auth (amplify_flutter v1.0.0-next.0). This new version is a full re-write of the auth category in dart, and it supports Mobile, Desktop, and Web.

You can read more about the developer preview release in the blog post and docs. I will update this issue again once this new version is out of developer preview.

[Jordan-Nelson]

This issue has been addressed in v1.0.0 of Amplify Flutter, which is now stable. This release also includes web and desktop support for Auth, API, Analytics, and Storage. You can see the list of new features and bug fixes in the release notes, and see more details on how to migrate in the upgrade guide.