Sencha Touch 2.x Forums /
Sencha Touch 2.x: Bugs /
[Sencha Cmd 184.108.40.206 / 220.127.116.11] Native apps fail on iOS 6 (run well on iOS 5)
Ext version tested: Sencha Touch 2.1.0 beta 3
Sencha Cmd 18.104.22.168 and 22.214.171.124 (versions for Windows)
Browser versions tested against: Mobile Safari (on iOS 5.1.1, then on iOS 6.0)
Description: Native apps built with Sencha Cmd 126.96.36.199 or 188.8.131.52 just fail when starting them on iOS 6 (and they run well on iOS 5)
Steps to reproduce the problem: Create a new app folder with
sencha generate app. Go inside that folder. Edit
packager.json to include actual applicationName, applicationId, bundleSeedId, and certificatePath for the iOS app and developer's credentials and certificate. Set platform to " iOS". Build a native app with
sencha app build native Install the new application on iPhone
Start the application on iPhone
The result that was expected: The application starts successfully both on iOS 5 and on iOS 6
The result that occurs instead: The application starts fine, as expected, on iOS 5
The application almost immediately fails when starting on iOS 6
Debugging already done: Possible fix:
Sencha - Sr Software Engineer
Thanks for the report! I have opened a bug in our bug tracker.
I too am having the same issue -- sencha touch app not working after ios 6 update
I think the issue is with the safari browser on the iPhone.<br>The following app --
www.diamondpro.com will not go beyond the start/splash screen.
Is the updated version with this fix already available for download? Or when will it be available?
Sencha Premium Member
I've tried downloading the nightly build of 2012-09-26, but it does not work in that build
If I understood correctly, they say will be available in
2.1.0-rc1 release. The latest available for download is still rb1.
Thanks for trying it and letting us know the result, Sven. BTW, have you tried just a recent nightly build of Sencha Touch 2 itself? or some updated (unreleased) version of Sencha Cmd v3 as well?
Though the status from Sencha indicates the issue is fixed in RC1, my understanding is that the issue is with Sencha Cmd, which needs to be fixed. And I assume that Sencha is planning to release an updated version of Sencha Cmd together with RC1 of Sencha Touch 2.
Thread Participants: 11
Tags for this Thread