Why Android App Links Open in the Browser Instead of Your App

Check the actual URL generated by your website, email, notification, QR code, or marketing campaign. Small differences can explain why some links open the application while others open the browser.

Step 4: Check Domain Verification Status

Android's verification behavior can differ by operating-system version and device implementation. Use the available Android Debug Bridge commands to inspect and test App Links on a connected device.

First, list the package's App Links information:

adb shell pm get-app-links com.example.shop

Replace com.example.shop with your application's package name.

On supported Android versions, the output provides information about the package's domain verification state and selected link-handling settings.

Look for the domain you expect to be verified. If verification has failed, review the manifest, asset links file, and signing certificate.

On devices that support it, you can request domain verification again:

adb shell pm verify-app-links --re-verify com.example.shop

Verification may take time. After running the command, inspect the status again rather than assuming the operation succeeded immediately.

These commands depend on Android version and platform tooling. If a command is unavailable on the target device, use the corresponding App Links tools or settings available for that version.

Step 5: Check the User's Link-Handling Settings

Even when the website association is correct, device settings can affect how links open.

A user may have previously chosen to open supported links in a browser or another application. Device manufacturers can also provide slightly different settings screens.

On many Android devices, you can check the application's settings:

1. Open Settings.
2. Select Apps.
3. Find your application.
4. Open the section for opening links or setting the app as the default.
5. Check whether supported links are allowed to open in the application.

The exact labels and menu locations vary by Android version and manufacturer.

This check is particularly important when App Links work on one device but consistently open in the browser on another.

Also test with a fresh installation or a clean test device when possible. Existing user preferences can make debugging results difficult to interpret.

Step 6: Test the Link With ADB

You can ask Android to resolve a URL without manually tapping a link in a browser.

For example:

adb shell am start \
  -a android.intent.action.VIEW \
  -c android.intent.category.BROWSABLE \
  -d "https://example.com/products/42"

This sends an implicit view intent containing the specified URL.

Observe which application Android opens and inspect the device logs if the result is unexpected.

If the browser opens, check the URL, the installed package, the manifest, domain verification, and user preferences.

If your application opens but displays the wrong screen, the App Links association may already be working. The remaining issue could be in the application's URL-routing logic.

Separating link resolution from in-app navigation helps narrow down the actual cause.

Step 7: Handle the Incoming URL in the Application

Opening the application is only half of the process. The activity must also interpret the incoming URL and navigate to the correct content.

For example, a Kotlin activity can inspect the incoming intent:

class ProductActivity : AppCompatActivity() {

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        handleIncomingLink(intent)
    }

    override fun onNewIntent(intent: Intent) {
        super.onNewIntent(intent)
        setIntent(intent)

        handleIncomingLink(intent)
    }

    private fun handleIncomingLink(intent: Intent) {
        val uri = intent.data ?: return

        if (uri.scheme != "https" ||
            uri.host != "example.com") {
            return
        }

        when {
            uri.pathSegments.firstOrNull() == "products" -> {
                val productId = uri.pathSegments.getOrNull(1)

                if (!productId.isNullOrBlank()) {
                    // Navigate to the product identified by productId.
                }
            }

            else -> {
                // Handle other supported routes or show a fallback screen.
            }
        }
    }
}

This example assumes that the activity uses AndroidX AppCompat and has the necessary imports. The navigation logic is intentionally left as an application-specific operation.

The onNewIntent() method matters when the activity is reused to handle a new link instead of being created again. Whether this callback is invoked depends on the activity's launch mode and the way Android launches it.

Validate incoming paths and identifiers before using them. A verified domain association does not mean every URL parameter is safe or valid.

Common Reasons App Links Open in the Browser

Best Practices for Production Applications

A reliable App Links implementation should be tested as part of the application's release process.

Use these practices:

• Keep the manifest's domain declarations aligned with the URLs generated by the website.
• Publish the correct Digital Asset Links file for every supported domain.
• Verify the signing fingerprint for the distributed application.
• Test links on the Android versions and devices supported by your application.
• Include tests for valid URLs, unsupported paths, missing identifiers, and malformed parameters.
• Test both fresh installations and upgrades.
• Keep the server-side asset links file available during domain or hosting changes.
• Monitor link-related failures reported by users and support teams.
• Make in-app navigation resilient when a link points to content that no longer exists.

For applications with multiple environments, use a deliberate strategy for development, staging, and production domains. Debug and release builds may have different package names or certificates, and each environment must be configured accordingly.

Summary

Android App Links can open in a browser when the URL does not match the intent filter, domain verification fails, the signing fingerprint is incorrect, or device settings affect link handling.

Start by checking the manifest and the Digital Asset Links file. Then inspect verification status, test the exact URL using ADB, and review the application's incoming-link handling.

Most importantly, distinguish between two problems: Android failing to route the URL to the application and the application opening but failing to navigate to the expected screen.

Testing both stages separately makes App Links issues easier to diagnose and helps prevent broken navigation from reaching production users.