Open slorber opened 7 years ago
Not sure it's related to the above PR/commits finally because I can reproduce the override by using v2.1.5.
Any idea on how we could avoid this override?
There's hopefully a workaround by configuring both plugin to support deep linking (note one use pathPrefix while the other use pathPattern params)
<universal-links>
<ios-team-id value="xxx" />
<host name="stample.co" scheme="https">
`<path url="/link/*" />
</host>
</universal-links>
<plugin name="cordova-plugin-customurlscheme" spec="4.2.0">
<variable name="URL_SCHEME" value="stample" />
<variable name="ANDROID_SCHEME" value="https" />
<variable name="ANDROID_HOST" value="stample.co" />
<variable name="ANDROID_PATHPREFIX" value="/link" />
</plugin>
I've found a better workaround for this issue.
It looks like config.xml declaration order matters. If I put <universal-links>
after the <plugin name="cordova-plugin-customurlscheme" spec="4.2.0">
, I am able to get the expected android manifest
Hi,
I need in my app both deep linking (with cordova-universal-links-plugin, not hacky redirect) and custom url scheme.
The "universal link" plugin needs to setup manifest:
But just afterward, the "custom url scheme" plugin overrides that declaration with:
I'm not an Android developer at all but this seems wrong to be. The documentation of Android mention that a data tag without at least a scheme does not make sense. Not sure what this plugin tries to achieve here: any idea?
Here's the commit from @EddyVerbruggen
It could be nice to make sure that both plugins work fine together. Thanks