Success! Looks like we've fixed this one. According to our records the fix was applied for
a recent build.
Sencha Cmd 126.96.36.199 fails to build navite iOS apps on Windows
Ext version tested:
- Sencha Cmd 188.8.131.52 (Windows version)
- Sencha Touch 2.0.1-b3
- Sencha Cmd 184.108.40.206 fails to build navite iOS apps on Windows
- The issue seems to appear when the native app package needs to be appropriately signed with the given certificate and developer credentials
Steps to reproduce the problem:
- Install Sencha Cmd 220.127.116.11 and Sencha Touch 2.0.1-b3 on the PC (in my case Sencha Cmd is installed in "C:\Program Files\")
- Go to the Sencha Touch directory and issue sencha generate app with some name and path to create the code base for a new ST app
- With an appropriate iOS developer and app's credentials and a certificate available (where those same credentials and certificate were successfully used to generate native apps with Sencha SDK 3.0.0 Beta 3 many times): Edit the applicationName, applicationId, bundleSeedId, and certificatePath in the packager.json file. Also change platform to "iOS".
- Build the native iOS app with sencha app build native.
The result that was expected:
- The native iOS app package is successfully built, like it was with Sencha SDK Tools in the past
The result that occurs instead:
- After the building sequence comes to "Packaging your application as a native app...", the stbuild.exe is aborted due to referencing a wrong memory address. (See the screenshot attached.)
- Building the native iOS app package is not finished
Screenshot or Video:
- See the screenshot attached
- Using sencha package build does not make any difference; the same application error.
- It is important to note that the issue does not appear when packager.json has platform set to "iOSSimulator". Thus I guess that the bug is related to signing the generated iOS app package with the given certificate.
- There is a recent report on Sencha Cmd 18.104.22.168 crashing on linux64 [TOUCH-3454]. I am not sure if these two issue have the same root cause or not. But based on that other report, from how I read it, they may potentially be related in some way.