[
https://issues.apache.org/jira/browse/CB-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985114#comment-13985114
]
Andrew Grieve commented on CB-6564:
-----------------------------------
I do understand the confusion, but I don't know how to go about fixing this.
The intention is that serve be used by setting your config.xml start page to
your server, not by loading the page up in a desktop browser. Desktop browser
is what cordova-browser is supposed to be about. Maybe we should warn based on
user-agent?
> `cordova serve` should report that it is unsupported
> ----------------------------------------------------
>
> Key: CB-6564
> URL: https://issues.apache.org/jira/browse/CB-6564
> Project: Apache Cordova
> Issue Type: Improvement
> Components: CLI
> Reporter: Shazron Abdullah
>
> https://issues.apache.org/jira/browse/CB-5475?focusedCommentId=13982020&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13982020
> See CB-5475
> The docs say it should work, and users will trust the CLI documentation that
> they can "cordova serve" and test with Android. This is especially
> problematic as it works fine with iOS. If there is not a fix planned for
> this, then the CLI should clearly warn folks (especially since the bug causes
> Chrome to lock up pretty fiercely) and I'd even suggest that the code behind
> serve specifically block a call to /adroid/www. Or even better, return a
> simple static message saying it is not supported.
> Basically my problem is that users have no way of knowing this isn't working,
> and until a proper fix/alternative exists, we should be more proactive about
> letting the user know
--
This message was sent by Atlassian JIRA
(v6.2#6252)
