Success! Looks like we've fixed this one. According to our records the fix was applied for TOUCH-3494 in a recent build.
  1. #31
    Sencha User VladimirTechMan's Avatar
    Join Date
    Jun 2012
    Location
    Russia
    Posts
    50
    Vote Rating
    4
    VladimirTechMan is on a distinguished road

      0  

    Default


    Great. Thanks, Alexander.

  2. #32
    Sencha User
    Join Date
    Aug 2009
    Posts
    16
    Vote Rating
    1
    zacjordaan is on a distinguished road

      0  

    Default


    That's great news. Good luck Alexander... I hope this issue can finally be put to bed and we can all get on with making great apps.

  3. #33
    Sencha User
    Join Date
    Aug 2009
    Posts
    16
    Vote Rating
    1
    zacjordaan is on a distinguished road

      0  

    Default FAIL

    FAIL


    Ok, I've tried every possible variation I can think of but still no success.

    On my Win 7 PC; iPhone 4S; iOS 6:

    Using sencha-touch-2.1.0-rc2 I generate a barebones app with "sencha generate app..."
    I edit the packager.json file with the same settings that worked with iOS 5.
    Using SenchaCmd-3.0.0.201-windows.exe I create a native build with "sencha app build native"

    Placing native package in iTunes and deploying to my iPhone... FAIL.

    I notice there's no _CodeSignature folder in my app but anyway I'm not sure if it's even supposed to be generated by the native build process? All certificate paths are correct - they work for iOS 5 builds.

    Ran a --debug log and the only part that may or may not mean something is:

    [DEBUG] executable located at C:\Users\johjordaz\bin\Sencha\Cmd\3.0.0.201\stbuild\stbuild.exe
    [DEBUG] using workding directory .
    [DEBUG] exit code was : -1073741819
    [DEBUG] exit code was : -1073741819
    [INFO ] Successfully packaged native application

    I'm officially out of ideas now.

  4. #34
    Sencha User VladimirTechMan's Avatar
    Join Date
    Jun 2012
    Location
    Russia
    Posts
    50
    Vote Rating
    4
    VladimirTechMan is on a distinguished road

      0  

    Default


    After doing a quick test this morning, I am absolutely glad to state that the issue is now eliminated (on Windows) with Sencha Cmd 3.0.0.230: The native builds are successfully signed and they also run fine on iOS 6!

    All those who's been waiting for the fix during the recent weeks should be very happy now. I certainly am.

    Many thanks to Sencha developers (and I'd like to say special thanks to Alexander Voloshyn) who worked to eliminate the issues with signing on Windows and running the packages on iOS 6.

  5. #35
    Touch Premium Member svenna's Avatar
    Join Date
    Jun 2007
    Location
    Oslo,Norway
    Posts
    568
    Vote Rating
    27
    svenna has a spectacular aura about svenna has a spectacular aura about

      0  

    Default


    PARTY - First initial test confirm that all my knows issues are resolved

    I can finally:
    - Build in Windows
    - Run on iOS 6
    - Open PDF etc in new window/browser

    ..Now I'll try the App Store upload.. I think my 6 month upload deadline is today
    (Last time with a working build I had not given up yet, now I have and there a Mac hidden in my office until apple allows uploads from other OS)
    Sven Tore Iversen

  6. #36
    Sencha User
    Join Date
    Nov 2012
    Posts
    1
    Vote Rating
    0
    Ugomobile is on a distinguished road

      0  

    Default Still problems on iOS 6 when building for production with Sencha Cmd 3.0.0.230.

    Still problems on iOS 6 when building for production with Sencha Cmd 3.0.0.230.


    Hi,

    Great work from all involved.

    I'm now also able to package a native app on window with Sencha Cmd 3.0.0.230 (and Sencha touch 2.0.1) and run it on iOS 6, but as long is the provision profile is for Debug.

    When I change the config.json file to Production and use a production provision profile, the native App fails on iOS 6, while the same App runs well on iOS 5

    Can anyone give me a tip, or do we still have a problem in Sencha Cmd 3.0.0.230+ ???

    Thanks,
    HJK

  7. #37
    Touch Premium Member
    Join Date
    Apr 2007
    Posts
    118
    Vote Rating
    -4
    hbeing123 can only hope to improve

      0  

    Default


    I got native to build and work with ios6 with the new CMD 3.0.0.230 but I can't get certain native functionalty to work, namely GPS and device openURL. GPS works on iOS5, openURL doesn't work at all.

  8. #38
    Touch Premium Member svenna's Avatar
    Join Date
    Jun 2007
    Location
    Oslo,Norway
    Posts
    568
    Vote Rating
    27
    svenna has a spectacular aura about svenna has a spectacular aura about

      0  

    Default


    I'm using openUrl now - works like a charm, but I'm using a nightly build 20121025
    Sven Tore Iversen

  9. #39
    Touch Premium Member
    Join Date
    Apr 2007
    Posts
    118
    Vote Rating
    -4
    hbeing123 can only hope to improve

      0  

    Default


    Hi Sven, I'm using RC2, but could you maybe share with me one of your openURL lines? I just want to make sure I have the syntax right.

  10. #40
    Touch Premium Member svenna's Avatar
    Join Date
    Jun 2007
    Location
    Oslo,Norway
    Posts
    568
    Vote Rating
    27
    svenna has a spectacular aura about svenna has a spectacular aura about

      0  

    Default


    Sure,

    I'm using this one to catch a click event on a a href link, pointing to a pdf.

    documentClick: function(event) {
    event.stopEvent();
    Ext.device.Device.openURL(event.target.getAttribute('href'));
    }
    Sven Tore Iversen