You have configured your Intent Filters in AndroidManifest.xml , hosted your assetlinks.json , and implemented the go_router or uni_links logic in Flutter. Yet, when you tap a link on an Android 12 or 13 device, it bypasses your app entirely and opens directly in Chrome. No "Open with..." dialog, no error logs in Flutter—just the browser. This behavior is not a bug in your routing code; it is a failure of the OS-level Domain Verification process introduced in Android 12 (API level 31). If the Android Domain Verification Agent cannot validate your site association with 100% certainty, it now defaults to the browser without prompting the user. Here is the root cause analysis and the rigorous solution to fix App Links verification. The Root Cause: API 31+ Verification Changes Prior to Android 12, if verification failed, Android relied on the "disambiguation dialog" (the bottom sheet asking the user to choose between the Browser or the App). ...
Android, .NET C#, Flutter, and Many More Programming tutorials.