Fixed
Status Update
No update yet.
Comments
il...@google.com
<intent-filter> elements don't support query parameters (so leaving them off the <intent-filter> is working as intended), but we should take into account the query parameters when determining uniqueness.
il...@google.com
I should add that this also makes the merged manifest attribution more complicated, since both destinations result in the same intent filter, which is perhaps confusing but correct. Ideally the merged manifest view shows links to both destinations on the generated <intent-filter>.
il...@google.com
ku...@google.com
il...@google.com
This has been fixed for a future build of Android Studio 3.5
Change-Id: I7ab90a3ed5783feecd5264e67e78b5ef3a277bcf
Change-Id: I7ab90a3ed5783feecd5264e67e78b5ef3a277bcf
sy...@gmail.com
This still happens, when using underscores in the URI on more than one entry.
jb...@google.com
Please file a new bug with a minimal sample project that reproduces your issue.
Description
Version used: 1.0.0-alpha09
Devices/Android versions reproduced on: Compile time
Error: "Manifest merger failed: Multiple destinations found with a deep link to
Situation:
- Two fragments with deep link URI's in a navigation graph
- Fragment A has a deep link URI without any query parameters
- Fragment B's deep link URI is the same as Fragment A's but with a query parameter
Expected behavior: A deep link with query parameters is unique from the same link without query parameters.
There was a recent bug fix in alpha07 that supported deep links with query parameters (
Sample app: