Force Open Chrome Custom Tab

[skybur]

So my App contains intent-filter for deep linking. When I tried to open link to my website inside the app (by launching custom tab using this library), it opens my app instead of the custom tab.

Is there a way to force it to open chrome custom tab instead of other app that could handle the links?

[tp]

We now also ran into this (through https://github.com/droibit/flutter_custom_tabs). Surprisingly this only happens on Samsung devices, and seems to be a new addition (would be very surprising otherwise if it went unnoticed this long).

I'll update this if we find more information.

@skybur I assume you also haven't found a workaround yet?

[tp]

What worked for me was to query the system which browsers support CCT, and then open that explicitly:

  fun getCustomTabsPackages(@NonNull context: Activity): ArrayList<ResolveInfo> {
    val pm = context.getPackageManager();
    // Get default VIEW intent handler.
    val activityIntent = Intent()
        .setAction(Intent.ACTION_VIEW)
        .addCategory(Intent.CATEGORY_BROWSABLE)
        .setData(Uri.fromParts("http", "", null));

    // Get all apps that can handle VIEW intents.
    val resolvedActivityList = pm.queryIntentActivities(activityIntent, 0);
    val packagesSupportingCustomTabs =  ArrayList<ResolveInfo>();
    for (info in resolvedActivityList) {
        val serviceIntent = Intent();
        serviceIntent.setAction(CustomTabsService.ACTION_CUSTOM_TABS_CONNECTION);
        serviceIntent.setPackage(info.activityInfo.packageName);
        // Check if this package also resolves the Custom Tabs service.
        if (pm.resolveService(serviceIntent, 0) != null) {
            packagesSupportingCustomTabs.add(info);
        }
    }

    return packagesSupportingCustomTabs;
  }

and then use it roughly like (checks etc. omitted):

customTabsIntent.intent.setPackage(getCustomTabsPackages(activity).get(0).activityInfo.packageName);

This works great for our case where we know the incoming link is definitely for our own domain. If it also might be external (e.g. Twitter), it would probably annoy the user if you alway open CCT. In that case this code path should only be run on request.