I reported the issue that you linked to. I'm trying to find a
workaround but have yet to see any possible way of getting things up
and running. Anyone out there with any thoughts? Or someone at
Google who can let us know the status of this?
I'm really hoping that someone just screwed up the emulator build and
that this won't affect the production builds...
tony
On Dec 7, 8:10 am, jsdf <jasons...@gmail.com> wrote:
Thanks for reporting it Tony.
I've contacted everyone I know at Google and outside.
I found one workaround, but it's ugly. I'll post it on the issue
itself.
On Dec 7, 4:07 pm, Tony <tony.cassan...@gmail.com> wrote:
> I reported the issue that you linked to. I'm trying to find a
> workaround but have yet to see any possible way of getting things up
> and running. Anyone out there with any thoughts? Or someone at
> Google who can let us know the status of this?
> I'm really hoping that someone just screwed up the emulator build and
> that this won't affect the production builds...
> tony
> On Dec 7, 8:10 am, jsdf <jasons...@gmail.com> wrote:
> > Hi all,
> > Has anyone played with the 2.3, WebViews, and the JavaScript to Java
> > interface?
> > If so, have you gotten it working?
At this point all we can do is vote for the issue (http://
code.google.com/p/android/issues/detail?id=12987 ) and hope it is an
"emulator only" issue or it gets fixed before the final build makes it
to the devices.
On Dec 8, 8:04 am, jsdf <jasons...@gmail.com> wrote:
> Thanks for reporting it Tony.
> I've contacted everyone I know at Google and outside.
> I found one workaround, but it's ugly. I'll post it on the issue
> itself.
> On Dec 7, 4:07 pm, Tony <tony.cassan...@gmail.com> wrote:
> > Hey,
> > I reported the issue that you linked to. I'm trying to find a
> > workaround but have yet to see any possible way of getting things up
> > and running. Anyone out there with any thoughts? Or someone at
> > Google who can let us know the status of this?
> > I'm really hoping that someone just screwed up the emulator build and
> > that this won't affect the production builds...
> > tony
> > On Dec 7, 8:10 am, jsdf <jasons...@gmail.com> wrote:
> > > Hi all,
> > > Has anyone played with the 2.3, WebViews, and the JavaScript to Java
> > > interface?
> > > If so, have you gotten it working?
Yeah, it's a bad pointer in the native libraries (which is why I'm
hoping someone just screwed up the emulator build and included a bad
library). You can see the pointer address is "deadd00d", which would
be humorous if it weren't such a terrible crash.
I also posted a comment with respect to your workaround. I think it'd
be easier to use the onJSAlert method to do what you've said, but that
still requires non-trivial rewrites of all code since you can't return
values without using callback chaining. Oh well...
Anyway, it'd be nice to get a response from someone at Google to let
us know the status of this. Does it affect hardware? Is this being
looked at? This could very well cause crashes of a huge number of
current apps in the market.
tony
On Dec 8, 7:02 am, Stefan <skyntc...@gmail.com> wrote:
> At this point all we can do is vote for the issue (http://
> code.google.com/p/android/issues/detail?id=12987 ) and hope it is an
> "emulator only" issue or it gets fixed before the final build makes it
> to the devices.
> On Dec 8, 8:04 am, jsdf <jasons...@gmail.com> wrote:
> > Thanks for reporting it Tony.
> > I've contacted everyone I know at Google and outside.
> > I found one workaround, but it's ugly. I'll post it on the issue
> > itself.
> > On Dec 7, 4:07 pm, Tony <tony.cassan...@gmail.com> wrote:
> > > Hey,
> > > I reported the issue that you linked to. I'm trying to find a
> > > workaround but have yet to see any possible way of getting things up
> > > and running. Anyone out there with any thoughts? Or someone at
> > > Google who can let us know the status of this?
> > > I'm really hoping that someone just screwed up the emulator build and
> > > that this won't affect the production builds...
> > > tony
> > > On Dec 7, 8:10 am, jsdf <jasons...@gmail.com> wrote:
> > > > Hi all,
> > > > Has anyone played with the 2.3, WebViews, and the JavaScript to Java
> > > > interface?
> > > > If so, have you gotten it working?
Hey guys, someone from google replied on the bug and said that this
does not happen on the Nexus S. So good news... Guess we'll have to
wait to test on device.
tony
On Dec 8, 11:25 am, Tony <tony.cassan...@gmail.com> wrote:
> Yeah, it's a bad pointer in the native libraries (which is why I'm
> hoping someone just screwed up the emulator build and included a bad
> library). You can see the pointer address is "deadd00d", which would
> be humorous if it weren't such a terrible crash.
> I also posted a comment with respect to your workaround. I think it'd
> be easier to use the onJSAlert method to do what you've said, but that
> still requires non-trivial rewrites of all code since you can't return
> values without using callback chaining. Oh well...
> Anyway, it'd be nice to get a response from someone at Google to let
> us know the status of this. Does it affect hardware? Is this being
> looked at? This could very well cause crashes of a huge number of
> current apps in the market.
> tony
> On Dec 8, 7:02 am, Stefan <skyntc...@gmail.com> wrote:
> > I also found this to cause be a repeatable crash in 2.3 emulator. The
> > crash log always starts with:
> > At this point all we can do is vote for the issue (http://
> > code.google.com/p/android/issues/detail?id=12987 ) and hope it is an
> > "emulator only" issue or it gets fixed before the final build makes it
> > to the devices.
> > On Dec 8, 8:04 am, jsdf <jasons...@gmail.com> wrote:
> > > Thanks for reporting it Tony.
> > > I've contacted everyone I know at Google and outside.
> > > I found one workaround, but it's ugly. I'll post it on the issue
> > > itself.
> > > On Dec 7, 4:07 pm, Tony <tony.cassan...@gmail.com> wrote:
> > > > Hey,
> > > > I reported the issue that you linked to. I'm trying to find a
> > > > workaround but have yet to see any possible way of getting things up
> > > > and running. Anyone out there with any thoughts? Or someone at
> > > > Google who can let us know the status of this?
> > > > I'm really hoping that someone just screwed up the emulator build and
> > > > that this won't affect the production builds...
> > > > tony
> > > > On Dec 7, 8:10 am, jsdf <jasons...@gmail.com> wrote:
> > > > > Hi all,
> > > > > Has anyone played with the 2.3, WebViews, and the JavaScript to Java
> > > > > interface?
> > > > > If so, have you gotten it working?
