In general, one intent filter has nothing to do with any other intent filter. That server does not respond with a .well-known/assetlinks.json – which means, that autoVerify="true" will fail. Consult the logcat output; it should complain about the failed verification.

One can check such .well-known/assetlinks.json with digitalassetlinks.googleapis.com.
When hosting a proper .well-known/assetlinks.json there, the response should look different:

{
  "maxAge": "600s",
  "debugString": "********************* ERRORS *********************n
                  None!n
                  ********************* INFO MESSAGES *********************n
                  * Info: No statements were found that match your queryn"
}

The Statement List Generator and Tester can be used to generate such an assetlinks.json.

One can also setup the <activity /> for implicit deep-linking:

<nav-graph android_value="@navigation/nav_graph"/>

Then use FragmentActivity to handle the deep link Intent with Navigation component.
Also see create an explicit deep link. It’s not so difficult when Navigation is set up already.

I’m currently creating a video player plugin app for my streaming website. This is because most browser don’t support some codecs. The app don’t have to show in the launcher category so I add this xml code to get rid of launcher icon.

<application
        android_allowBackup="true"
        android_icon="@mipmap/ic_launcher"
        android_label="@string/app_name"
        android_roundIcon="@mipmap/ic_launcher_round"
        android_supportsRtl="true"
        android_theme="@style/Theme.MyApplication"
        android_usesCleartextTraffic="true" >
        <activity
            android_name=".MainActivity"
            android_exported="true" >
            <intent-filter>
                <action android_name="android.intent.action.MAIN" />
            </intent-filter>
            <intent-filter android_autoVerify="true" >
                <action android_name="android.intent.action.VIEW" />

                <category android_name="android.intent.category.DEFAULT" />
                <category android_name="android.intent.category.BROWSABLE" />

                <data
                    android_host="streameo.page.link"
                    android_scheme="https" />
            </intent-filter>
        </activity>
    </application>

But when I integrate Firebase dynamic link, it’s not opening app, but after adding the launcher category back it’s working. Is there a work around?