Android中能否动态设置Deep Linking URI，替代AndroidManifest配置？

Great question! Let's break this down clearly:

Short Answer #

You can't directly add or modify deep link URIs that the Android system recognizes at runtime (since the system parses your AndroidManifest.xml during app installation to map URIs to your app). But you can implement a flexible workaround to dynamically control which URIs your app actually processes.

Detailed Explanation #

1. Why static manifest configuration is required #

Android's Package Manager scans your app's AndroidManifest.xml during installation to register all <intent-filter> entries, including those for deep links. This is how the system knows which app to launch when a user clicks a matching URI. The system doesn't re-scan the manifest at runtime, so any new URIs added after installation won't be recognized by the system.

2. Workaround: Broad static filter + runtime validation #

To achieve dynamic control over which URIs your app handles, you can:

• Configure a broad, catch-all <intent-filter> in your manifest that covers all potential URIs you might want to handle later.
• Maintain a dynamic list of allowed URIs (e.g., fetched from your backend) and validate incoming deep links against this list at runtime.

Example Implementation

Step 1: Add a broad intent filter in AndroidManifest.xml

<activity android:name=".DeepLinkRouterActivity">
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <!-- Catch all URIs with your app's scheme and any host/path -->
        <data android:scheme="yourapp" android:host="*" />
    </intent-filter>
</activity>

Step 2: Validate and handle deep links at runtime (Kotlin example)

class DeepLinkRouterActivity : AppCompatActivity() {
    private var allowedDeepLinks: Set<String> = emptySet()

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        // Fetch allowed URIs from your backend (replace with actual network call)
        fetchAllowedDeepLinks()
        // Handle the incoming deep link
        intent?.let { processDeepLink(it) }
    }

    override fun onNewIntent(intent: Intent?) {
        super.onNewIntent(intent)
        // Handle deep links when the activity is already running
        intent?.let { processDeepLink(it) }
    }

    private fun processDeepLink(intent: Intent) {
        val incomingUri = intent.data ?: return
        val uriString = incomingUri.toString()

        if (allowedDeepLinks.contains(uriString)) {
            // Navigate to the corresponding screen
            navigateToTargetScreen(incomingUri)
        } else {
            // Reject the invalid deep link (e.g., show error or close the activity)
            Toast.makeText(this, "Invalid deep link", Toast.LENGTH_SHORT).show()
            finish()
        }
    }

    private fun fetchAllowedDeepLinks() {
        // Simulate fetching from backend
        allowedDeepLinks = setOf(
            "yourapp://product/101",
            "yourapp://profile/202",
            "yourapp://promo/summer-sale"
        )
    }

    private fun navigateToTargetScreen(uri: Uri) {
        // Route to the appropriate screen based on URI
        when (uri.host) {
            "product" -> {
                val productId = uri.pathSegments.firstOrNull()
                // Launch product detail activity with productId
            }
            "profile" -> {
                val userId = uri.pathSegments.firstOrNull()
                // Launch profile activity with userId
            }
            "promo" -> {
                val promoCode = uri.pathSegments.firstOrNull()
                // Launch promo activity with promoCode
            }
        }
    }
}

3. Caveats to note #

• Broad filter tradeoff: All URIs matching your broad scheme/host will trigger your activity first, even if they're not in your allowed list. This means your app may briefly launch before rejecting invalid links.
• App Links limitation: For Android App Links (verified deep links requiring assetlinks.json), you can't dynamically modify the verified domains—these are validated by the system during installation and can't be changed at runtime.

Final Takeaway #

While you can't make the Android system recognize entirely new deep link URIs at runtime, the workaround above lets you dynamically control which URIs your app actually processes, covering most practical use cases.

内容的提问来源于stack exchange，提问作者zundi