Not supported valid URIs for deeplinks with same path and different number of parameters about deeplinkdispatch

[rossbacher]

Sorry it took that long but this is fixed now and in release https://github.com/airbnb/DeepLinkDispatch/releases/tag/5.3.0.

[rossbacher]

I'll have a look at that. I don't think we have a test case for this and thus it might have been missed.

[stari4ek]

There is a chance that incremental build is involved.
I had same issue. Bunch of "foo://navigate/*" declared, but only one was added to registry.

It looks like it swallows errors, so only part of entries are added. And it stays unchanged on next build.

I had:

@AppDeepLink({"tv/{what}"})
public static Intent intentForTv(@NonNull Context context, @NonNull Bundle extras) {

Dropped placeholder from link:

@AppDeepLink({"tv"})
public static Intent intentForTv(@NonNull Context context, @NonNull Bundle extras) {

No errors, but registry got 2 entries only (10+ expected).
Changed signature:

@AppDeepLink({"tv"})
public static Intent intentForTv(@NonNull Context context) {

Same broken registry.
Forced to rebuild project => registry recovered.

Updated:

Maybe I'm hi-jacking the issue after all. According to initial report - registry is populated with both entries which is different from my case when registry become broken.
I have disabled kapt.arguments.deepLink.incremental and do not have issues so far:

@AppDeepLink({
    "navigate/tv/{kind}",
    "navigate/tv/{kind}/{id}"
})

produces:

new DeepLinkEntry("myapp://navigate/tv/{kind}/{id}", DeepLinkEntry.Type.METHOD, DeepLinksTvNavigation.class, "intentForTv"),
new DeepLinkEntry("myapp://navigate/tv/{kind}", DeepLinkEntry.Type.METHOD, DeepLinksTvNavigation.class, "intentForTv"),

and both are resolved as expected.

[cvillaseca]

Thank you for the fix @rossbacher 🙏