We also stumbled upon what seems to be the same issue. We tracked it down
to javascript in iOS6 behaving strangely in the canCastUnsafe method that
is used whenever a java typecast is done. In our case, this only happend
when attempting to cast a String value and it only seems to happen in
rela
Found any solution?
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/o-VzRHjg4T4J.
To post to this group, send email to google-web-toolkit@google
We haven't done anything else for the moment. We hope iOS 6.1 or the next
version of GWT fixes it.
By the way, probably related bug:
http://code.google.com/p/google-web-toolkit/issues/detail?id=7831
Maybe if you (and more people) star it the GWT team will prioritize it (and
will either fix it
So how do you handle the situation?
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/nus-8ne96tcJ.
To post to this group, send email to google-w
Yes. The problem is that I cannot reproduce the crash every time. I have a
view which sometimes crashes (safari just closes), but there is no specific
way to reproduce the crash. It just sometimes happens. When I look at the
crash report of the ipad, it just says invalid memory access. It looks
No. It still persists.
Are you facing a similar problem ?
Oscar
El lunes, 14 de enero de 2013 20:54:41 UTC+1, mkn escribió:
>
> Hi
>
> Could you solve your problem in the meantime?
>
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To
Hi
Could you solve your problem in the meantime?
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/7k89_Qu4jloJ.
To post to this group, send emai
Hi.
Unfortunately I don't have a Mac. But I compiled in PRETTY mode without
ClosureCompiler and I have isolated one of the points where iOS 6 crashes.
In this case there is no exception thrown. Javascript just halts.
In the following code, the first alert ('before PriceEvol') is displayed,
but
Can you:
1.) compile your app in PRETTY mode so you can read JS source code easily
2.) enable iOS inspector and use Safari 6 on Mac OS to connect to your
iphone/ipad for remote debugging
(http://moduscreate.com/enable-remote-web-inspector-in-ios-6/)
3.) In Safari 6 web inspector go to "breakpoin
Yes, the error that we are gettting is a ClassCastException.
Oscar
El miércoles, 7 de noviembre de 2012 14:39:15 UTC+1, Daniel Kurka escribió:
>
> Do you have a uncaught exception handler in place so that we could maybe
> get at least a JavaScript error?
>
> -Daniel
>
>
> On Wednesday, November
Do you have a uncaught exception handler in place so that we could maybe
get at least a JavaScript error?
-Daniel
On Wednesday, November 7, 2012 11:54:57 AM UTC+1, Óscar Frías Barranco
wrote:
>
> Just let me clarify that the ClosureCompiler does not fix the issue, it
> just makes it less freq
Just let me clarify that the ClosureCompiler does not fix the issue, it
just makes it less frequent.
The issue is so weird that you can load a GWT page without any error and
then just reload the same page to find that now GWT javascript crashes.
And then reload again and its OK. It's complete
Hi again.
We have found that compiling with -XenableClosureCompiler hides the problem
or at least mitigates it.
I have no idea about what Closure Compiler does to GWT generated javascript
but apparently it is hiding iOS6 browser issues.
Oscar
El martes, 6 de noviembre de 2012 11:15:10 UTC+1,
Hello.
Our GWT application crashes when running on an iPad with iOS 6.0.1.
This is not related to the POST caching issue because we already added
Cache-Control and Expires headers to GWT RPC replies and now they are not
cached.
We have "debugged" the app by adding Window.alert() calls and we h
14 matches
Mail list logo
