incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Bowser <>
Subject Re: [Android] - Merging CordovaWebView into Master this week?
Date Wed, 09 May 2012 21:48:56 GMT

I just reverted back to the to the other branch and I'm getting this as
well on Cordova:
D/CordovaLog( 2840): JSCallback Server Closed: Stopping callbacks.
D/CordovaLog( 2840): file:///android_asset/www/cordova-1.7.0.js: Line 3560
: JSCallback Server Closed: Stopping callbacks.
I/Web Console( 2840): JSCallback Server Closed: Stopping callbacks. at

I'm suspecting that the issue is the fact that we shut down and re-start
the server every time we go from one page to another.  I do notice that
certain Jasmine specs aren't working on the latest version of the code, and
I would definitely appreciate any help figuring out why.

Still, I really think we should merge this into 1.8 before we release an


On Wed, May 9, 2012 at 1:56 PM, Joe Bowser <> wrote:

> On Wed, May 9, 2012 at 1:42 PM, Simon MacDonald <
> > wrote:
>> Should I be using a particular file when doing my
>> testing? I'm using the latest from the js project. When I do I get a
>> few errors:
>> 1) Trying to get a persistent FS fails so most of the automatic file
>> tests fail.
> I'll take a look at it now.  Last time I ran the tests it passed.
>> 2) Every call returns a variation of:
>> I/Web Console( 1103): JSCallback Error: Request failed. at
>> file:///android_asset/www/
>> but it appears that he call that I've made succeeds.
> Strange!
>> Other comments:
>> 1) Plugins will break again. Every plugin I've tried (Barcode,
>> ChildBrowser, TTS, VideoPlayer, etc.) has required changes in the Java
>> code in order to compile.
> I'm OK with this breakage if we document it. There's no way we can get
> around not breaking plugins with this change, but It doesn't mean that we
> shouldn't do it.
>> 2) I don't like how "ctx" is a CordovaInterface but is casted to
>> Activity or Context depending on what is required.
> ctx is NOT a CordovaInterface.  ctx is now a Context,like it was before we
> started overly relying on DroidGap. CordovaInterface is something that we
> recommend that people implement if they want their random activity to work
> with certain plugins that require parts of the Android Life Cycle.  This is
> because we can't guarantee that we're using an Activity, a DroidGap or a
> CordovaInterface, and we have to account for some people not listening to
> us.  That's why we wrote CordovaException to be thrown for these plugins.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message