You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Joe Bowser (JIRA)" <ji...@apache.org> on 2013/01/15 10:06:12 UTC

[jira] [Resolved] (CB-2222) JSCallback Server Closed: Stopping callbacks

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

Joe Bowser resolved CB-2222.
----------------------------

    Resolution: Won't Fix

We deprecated the callback server back in September 2012 since there is a known bug with Android 4.x that we can't fix where if you go offline and go online, the callback server loses the connection.  This is exempt from our current deprecation policy because this was in response to a change Google made in Android that broke Cordova.

We highly recommend upgrading to Cordova 2.2.0 or later, since the performance is greatly increased, and it actually works on Android 4.x and above. 
                
> JSCallback Server Closed: Stopping callbacks
> --------------------------------------------
>
>                 Key: CB-2222
>                 URL: https://issues.apache.org/jira/browse/CB-2222
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 2.0.0, 2.1.0
>         Environment: Acer Iconia A210, ic1754f, Android 4.1.1, kernel 3.1.10+
>            Reporter: Martin Ambrus
>            Assignee: Joe Bowser
>              Labels: android, callback
>
> We use jQuery Mobile to navigate thorough pages in our application. Those pages are being loaded externally from our server, then displayed in the Cordova's WebView inside our application.
> Once the first navigation occurs, all callbacks to Cordova are stopped and the following message appears: JSCallback Server Closed: Stopping callbacks
> Unfortunately I don't have access to this tablet directly, so I can't debug it - it's a customer's tablet and I was only able to see logs for a brief moment when I had it connected to my PC via USB.

--
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