[
https://issues.apache.org/jira/browse/CB-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865521#comment-13865521
]
Andrew Grieve commented on CB-5446:
-----------------------------------
I think maybe what's needed here is just some explanation of how to get around
the whitelist restriction.
Will putting the scheme in the whitelist make it work? Or is the only option to
write a plugin that will fire the intent? Maybe we should provide a built-in
plugin to fire simple intents instead of users trying to use links for doing so?
> Custom URLs not supported since Cordova 3.0
> -------------------------------------------
>
> Key: CB-5446
> URL: https://issues.apache.org/jira/browse/CB-5446
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 3.0.0, 3.1.0
> Environment: Any Android device! Tested on Nexus S (2.3.6), Nexus 4
> (4.3), Samsung Galaxy S (2.3.3), HTC One X (4.1.2)
> Reporter: Steve
> Assignee: Joe Bowser
> Priority: Minor
>
> When I add a custom URL in my html page, for example:
> <a href="myapp://test/testing.html">Link that opens another Android app</a>
> If I click on the link, I am getting an error "Application Error" with the
> content:
> "The protocol isn't supported. (myapp://test/testing.html)"
> This issue does not exist in Cordova 2.x. You can try this by cloning the
> following github repo (https://github.com/Icenium/sample-custom-url-scheme)
> and install the app on your Android device. Then from another Android app,
> create a hyperlink that uses the custom URL scheme that the first app listens
> to e.g. "myapp://".
> Note: The sample app uses WebIntent plugin. The plugin itself works fine with
> Cordova 3.0 and can be downloaded from
> https://github.com/Initsogar/cordova-webintent.
> P.S. I saw similar problem in this Jira issue
> https://issues.apache.org/jira/browse/CB-3902. The fix to hardcode market://
> seems to avoid fixing this GENERAL problem.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
