[jira] [Commented] (CB-5475) 'cordova serve' not working

2014-04-29 Thread Shazron Abdullah (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985031#comment-13985031
 ] 

Shazron Abdullah commented on CB-5475:
--

Sorry Ray, I understand completely, I've filed a separate issue: CB-6564

> 'cordova serve' not working
> ---
>
> Key: CB-5475
> URL: https://issues.apache.org/jira/browse/CB-5475
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CLI
>Affects Versions: 3.2.0
> Environment: Mac OSX 10.9. Chrome. 
>Reporter: No Ducks
>
> Probably an old bug, but how and ever.. 
> Downloaded this version (3.2.0-0.1.0) of Cordova today. built a new project, 
> and tried to run it with `cordova serve`  -  
> clicked 'android' ... got the gap errors ...
> gap:["PluginManager","startup","PluginManager1669056395"]
> 'clicked ok' and got about 50,000 of these messages in the console.
> processMessage failed: invalid message: 
> Thought I'd ask here.. slightly related... I only need the File API plugin 
> for my project.  So, was wondering - is it recommended by Apache to use 
> 'ripple emulate' or 'cordova serve' for browser testing? 



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CB-5475) 'cordova serve' not working

2014-04-26 Thread Raymond Camden (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982020#comment-13982020
 ] 

Raymond Camden commented on CB-5475:


Why is this resolved as not a problem? Unless someone knows this bug exists, 
they 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.

> 'cordova serve' not working
> ---
>
> Key: CB-5475
> URL: https://issues.apache.org/jira/browse/CB-5475
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CLI
>Affects Versions: 3.2.0
> Environment: Mac OSX 10.9. Chrome. 
>Reporter: No Ducks
>
> Probably an old bug, but how and ever.. 
> Downloaded this version (3.2.0-0.1.0) of Cordova today. built a new project, 
> and tried to run it with `cordova serve`  -  
> clicked 'android' ... got the gap errors ...
> gap:["PluginManager","startup","PluginManager1669056395"]
> 'clicked ok' and got about 50,000 of these messages in the console.
> processMessage failed: invalid message: 
> Thought I'd ask here.. slightly related... I only need the File API plugin 
> for my project.  So, was wondering - is it recommended by Apache to use 
> 'ripple emulate' or 'cordova serve' for browser testing? 



--
This message was sent by Atlassian JIRA
(v6.2#6252)