[
https://issues.apache.org/jira/browse/CB-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272674#comment-13272674
]
Filip Maj commented on CB-680:
------------------------------
Interestingly, I cannot reproduce with the Accelerometer. Using the stock
example that comes with cordova-android currently, if I call
{{navigator.accelerometer.watchAcceleration}} inside the {{deviceready}}
callback, it works fine and no errors are reported in logcat on my Galaxy Nexus
running 4.0.2.
Joe mentioned that this was coming up while using the File API, so I will
investigate with calling {{resolveLocalFileURI}} inside {{deviceready}}.
> onNativeReady fires before the server is taking new connections
> ---------------------------------------------------------------
>
> Key: CB-680
> URL: https://issues.apache.org/jira/browse/CB-680
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: Android
> Affects Versions: 1.7.0
> Reporter: Joe Bowser
> Assignee: Filip Maj
> Priority: Blocker
> Fix For: 1.8.0
>
>
> This issue is able to be ignored in Android 1.7, but it has come to a head in
> Android 1.8, since we moved where the Callback Server lives.
> D/CordovaLog( 3395): file:///android_asset/www/cordova-1.7.0.js: Line 3570 :
> JSCallback Error: Request failed.
> When this occurs, and you have methods that are called onDeviceReady, while
> the interfaces exist, there's no way to get the callback, which means that it
> hangs forever and always fails when using the CordovaWebView branch. This
> indicates that we are calling onNativeReady prematurely when we go from page
> to page, and that we have to wait for the server to be ready before calling
> this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
