14 Oct 2011 11:25 AM #1
Sencha Touch in iOS5 doesn't work anymore, even Kitchensink fails
Platform tested against:
- iOS 5.0
- iPAD1 & iPAD2
Steps to reproduce the problem:
- Go to Kitchen sink demo page in iOS5 Safari and start navigate to different screens. When I tested in iPad1 it took some time to throw the timeout exception but in iPad2 it just showed the exception in the very first screen ( as soon I pressed "User Interface" in the left bar).
- Work as normal
Debugging already done:
14 Oct 2011 12:03 PM #2
Ditto for ST 2.0 Kitchen Sink - timeout exception right away in iOS 5 iPad 2.
14 Oct 2011 12:24 PM #3
It's a browser problem, most likely. Once err starts it goes on til browser restarted
I killed the browser and restarted it - then navigated to ST KitchenSink and had no problem, no exceptions in the beginning. Then after doing different things on different pages, dreaded timeout exception occurred, and since then everything: our app, ST samples - started throwing this error. Even after page is refreshed, script timeout errors are everywhere.
14 Oct 2011 3:35 PM #4
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Just tried both ST 1.1.0 kitchen sink and ST 2.0 PR1 kitchen sink on iPad 2 with iOS 5 and my new (and shiney) iPhone 4S with iOS 5 and both work no problems. In fact, to me my iPhone seemed faster than my iPad.Mitchell Simoens @LikelyMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
17 Oct 2011 1:48 AM #5
That's weird. It works excellent on my iPad 2 with iOS 5. Same on a colleague.
17 Oct 2011 7:32 AM #6
Others having same issue
It's not Sencha error, but Sencha needs to pay attention and maybe help with finding the work-around or getting this problem on Apple's radar ASAP.
23 Oct 2011 10:53 AM #7
iPhone 4 running iOS 5.
Works fine in the simulator or a desktop browser (Chrome).
Throws the error on the phone.
If I force quit mobile Safari on the phone the error goes away and the app will load.
24 Oct 2011 4:24 AM #8
Looks like an OS bug. (see also http://stackoverflow.com/questions/7...ceeded-timeout )
24 Oct 2011 5:39 AM #9
Have any of you guys found any solution for this problem?
29 Oct 2011 1:51 PM #10
It looks like there is an issue with the 'autoUpdate' feature of the Ext.util.GeoLocation. Setting that to false caused this issue to stop occurring.
This may not fix it for everyone, but it did in my app.
Related thread on stackoverflow: http://stackoverflow.com/questions/7...ceeded-timeout