incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bowser (JIRA)" <>
Subject [jira] [Resolved] (CB-680) onNativeReady fires before the server is taking new connections
Date Thu, 10 May 2012 22:14:48 GMT


Joe Bowser resolved CB-680.

    Resolution: Fixed
      Assignee: Joe Bowser  (was: Filip Maj)

The fix was related to when the callback server actually starts and stops.  It doesn't make
sense for the callback server to be stopped and restarted on loadUrl, and instead it should
happen on the onPageStarted in the CordovaWebViewClient.  That being said, I'm not sure why
we are doing this at all, but that discussion should take place on the list.
> onNativeReady fires before the server is taking new connections
> ---------------------------------------------------------------
>                 Key: CB-680
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Sub-task
>          Components: Android
>    Affects Versions: 1.7.0
>            Reporter: Joe Bowser
>            Assignee: Joe Bowser
>            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 message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message