You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Ramki G (JIRA)" <ji...@apache.org> on 2013/06/09 11:13:20 UTC

[jira] [Commented] (CB-3387) deviceready doesn't fire in Chrome Ripple

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

Ramki G commented on CB-3387:
-----------------------------

The issue persists in Cordova 2.8.0 as well
                
> deviceready doesn't fire in Chrome Ripple
> -----------------------------------------
>
>                 Key: CB-3387
>                 URL: https://issues.apache.org/jira/browse/CB-3387
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CordovaJS
>    Affects Versions: 2.7.0
>         Environment: Ripple for Chrome
>            Reporter: Andy Van De Walle
>            Assignee: Filip Maj
>            Priority: Minor
>
> Applications with cordova 2.7 don't seem to work in Ripple (android is just fine).  Following error message shows up:
> Ripple :: Environment Warming Up (Tea. Earl Gray. Hot.) ripple.js:37
> GET http://localhost/workspace/Scan2Order/assets/www/config.xml 404 (Not Found) ripple.js:50
> cordova :: Initialization Finished (Make it so.) ripple.js:37
> GET http://localhost/workspace/Scan2Order/assets/www/cordova_plugins.json 404 (Not Found) ripple.js:50
> Uncaught SyntaxError: Unexpected token < cordova.js:6816
> deviceready has not fired after 5 seconds. cordova.js:6672
> Channel not fired: onPluginsReady cordova.js:6665
> Channel not fired: onCordovaReady cordova.js:6665
> Channel not fired: onCordovaConnectionReady cordova.js:6665
> deviceready has not fired after 5 seconds. cordova.js:6672
> Channel not fired: onPluginsReady cordova.js:6665
> Channel not fired: onCordovaReady cordova.js:6665
> Channel not fired: onCordovaConnectionReady cordova.js:6665

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira