Re: GWT WebApp and iOS 6 Safari

Enrico, thanks for noting your solution here. I've been battling with the same issue and while your solution didn't work exactly for me (I don't know why) it allowed me to find another way relatively easily. For anyone else who comes across this I had to first inherit logging (I wasn't using it before) then I needed to disable the handlers in my .gwt.xml file:

  <inherits name="com.google.gwt.logging.Logging"/>

  <set-property name="gwt.logging.consoleHandler" value="DISABLED"/>

  <set-property name="gwt.logging.developmentModeHandler" value="DISABLED" />

  <set-property name="gwt.logging.popupHandler" value="DISABLED" />

  <set-property name="gwt.logging.systemHandler" value="DISABLED" />

  <set-property name="gwt.logging.firebugHandler" value="DISABLED" />

  <set-property name="gwt.logging.simpleRemoteHandler" value="DISABLED" />

I suspect you'd only need to disable gwt.logging.consoleHandler but I disabled all since I don't need them.

I'm pretty sure this is caused by a bug in the IOS 6 version of Safari. My suspicions are compounded by the fact that if the IOS Safari is run under Apple's remote debugger (connected to Safari on a Mac) the class cast exception never happens, presumably because they then swap in a different JS console outlet at a low level . I hope they fix this soon as I think adding then disabling the logging adds a good few KB to the weight of my .cache.html files.

As of now (late Dec 2012) Apple don't appear to be fixing it (I tested with the 6.1 beta due for release early 2012). Here's hoping they sort it so I / others can remove this ugly hack.

Jon 

On Thursday, 4 October 2012 18:57:24 UTC+1, Enrico wrote:

Ok I finally found what's going on.

Removing the logger definition from RegisterPlace caused the exception not be thrown, but the app was still crashing (after RegisterPlace instantiation and before the related activity start, probably on PlaceController).

Setting logging disabled in my gwt.xml finally solve the issue:
<set-property name="gwt.logging.enabled" value="FALSE" />

Hard to believe but I figure that there is something in logging framework that is interfering with IOS 6 Safari.
I really think this is going to impact all GWT Apps that run on IOS 6 Safari.

Hope it helps.

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