Grant schrieb: > I have been working on an app that works without fail on desktop > browsers and on iPhone when it is connected by wireless network. > Frustratingly it will sometimes fail to run when connected by 3G. The > symptom is you load the page and just get a blank screen.
Check the server-log if all files that are needed are actually requested and completely transfered. > iPhone debugging is limited, but turning on the dev console displays > no errors. Of course the emulator connects over broadband so cannot > reproduce it there. AFAIR you can debug an application running remotly on the usb-connected device instead of in the emulator. But if that helps for a web-application I don't know. > It will not always fail in 3G, sometimes it works all day but other > days not at all (without me having uploaded a new version of the app), > but as stated before will always run under wifi. My theory is that the transfer of one of the javascript-files gets interrupted. After reestablishment of the 3G-connection, the browser is requesting the rest of the file (using the Range-HTTP-Request-header). Some servers and also some client (like Adobe Acrobat) have had a couple of bugs in the imple- mentation of range-request-handling leading to corrupted data on client-side. Switching of range-support on server-side should allow you to test this theory. Regards, Lothar
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
