If the onDeepLinkNoMatch() called once, then both of my onDeepLinkā¦ functions do not trigger.
The deeplink is captured because I can see in the console:
On deep link
Object {url: ...
The only way to bypass this, is to re-subscribe when the onDeepLinkNoMatch() is called.
But then, Iām starting seeing two console.log entries of āOn deep linkā¦ā messages.
If another unmatched deeplink occurs, and I subscribe again, then I see 3 āOn deep linkā¦ā messages in console.log. And so on.
Using
this.eventSubscription.unsubscribe();
before subscribing anew, does not help.
Is the team aware of this behavior?
Or am I doing something wrong?
Agree with @killerchip, I faced that this week too, I think itās an issue (on my comment at the bottom I tried to link the possible duplicated issues):
As you, the only workaround I found so fat was subscribing again when there is a nomatch
@killerchip it was maybe a clever move, ionic-plugin-deeplinks has been now marked as āNO LONGER MAINTAINEDā with branch.io as recommended solution
And this is why people go native, because of bad support like this, 2 years old and still the same issue. The module is poorly coded. The problem is @ionic-native/deeplinks. Observable should NOT be used here.