Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Date: Thu, 10 May 2012 18:18:52 +0000 (UTC)
From: "Joe Bowser (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: 
 <1103707989.50579.1336673932379.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1936938712.47110.1336606669817.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (CB-680) onNativeReady fires before the server is
 taking new connections
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CB-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bowser reassigned CB-680:
-----------------------------

    Assignee: Filip Maj  (was: Joe Bowser)
    
> 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