Given a navigation file with entry

        <deepLink app:uri="*.seatgeek.ca/e/performers/{id}" />

the resulting manifest (copied from the APK analyzer AS tool) will look like

            <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:scheme="http" />

                <data
                    android:scheme="https" />

                <data
                    android:pathPrefix="/e/performers/" />
            </intent-filter>

which is missing the required <data android:host="*.seatgeek.ca" />. As a result, the browser picks up such links instead of being directed into the app. I also verified in the Merged Manifest subview of AndroidManifes.xml that it's missing there.

I did try manually adding the <intent-filter /> with the proper host, scheme, etc and confirmed that navigation is properly routing when it does receive that intent, so the problem appears just to be within the manifest generation from the navigation XML.

Build: AI-223.7571.182.2231.9523943, 202301250042, 

AI-223.7571.182.2231.9523943, JRE 17.0.5+0-17.0.5b653.25-9484017x64 JetBrains s.r.o., OS Linux(amd64) v5.4.0-137-generic, screens 3840.0x2160.0, 3840.0x2160.0, 3840.0x2160.0, 3840.0x2160.0

AS: Giraffe | 2022.3.1 Canary 2
Kotlin plugin: 223-1.7.21-AS7571.182
Android Gradle Plugin: 7.3.1
Gradle: 7.4
Gradle JDK: JetBrains Runtime version 17.0.5
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)