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 "breakpoints" and activate "all 
exceptions" or "uncaught exceptions" and then check the call stack once the 
exception occurs. 

Maybe that gives you some hints which generated JS code exactly causes the 
unexpected exception.


-- J. 



Am Mittwoch, 7. November 2012 17:01:46 UTC+1 schrieb Óscar Frías Barranco:
>
> 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 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 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 completely random.
>>>
>>>
>>> El martes, 6 de noviembre de 2012 19:51:51 UTC+1, Óscar Frías Barranco 
>>> escribió:
>>>>
>>>> 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, Óscar Frías Barranco 
>>>> escribió:
>>>>>
>>>>> 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 have 
>>>>> found that it crashes (randomly, not always) in places like:
>>>>>
>>>>> HashSet.add() method
>>>>> RootPanel.add() method (which includes a HashSet.add() call)
>>>>> ConstantsWithLookup.getString()
>>>>>
>>>>>
>>>>> It looks like iOS 6 Javascript engine has some issues, so maybe GWT is 
>>>>> being bitten by these errors too:
>>>>>
>>>>>
>>>>> http://stackoverflow.com/questions/12534409/ios-6-javascipt-intermittent-issues-with-object-defineproperty
>>>>>
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Thanks,
>>>>> Oscar
>>>>>
>>>>>
>>>>>

-- 
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/-/0KYVMl5jLpIJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to