Use XCode6.0.1 to package the cocos2d-x3.1 project with IPA (support iOS8)

It is said that iOS8 need to use XCode6.1 packaging, because it has not been upgraded, temporarily studied for a few days, first put the notes sorted, for later use convenient, because I do not have an iphone, no Apple Enterprise certificate, all things are patchwork, so packaged into the IPA no real machine test. If it fails, it will only be studied again.

Because of the need to upgrade the project support IOS8 3.1 projects, the two days temporarily studied the packaging of IPA (before others, the first time their own packaging, or very laborious) all, there is this article, if possible, let everyone less detours, put time as much as possible in writing code , but I still have to spit it out: it's really hard for Apple to make this set.

1, Problem 1:3.1 project temporarily does not support iOS8because 3.1 time IOS8 has not been released, so, 3.1 does not support IOS8, due to iOS8 the bottom part of the changes, may compile 3.1 works to the simulator or the real machine will encounter the problem in this article, can refer to this article to solve. 2. Question 2: How to Package Enterprise certificate into IPAbecause I am a registered Apple developer, the enterprise account is also a friend to give, so, the packaging of the IPA here may not be very formal, and has not been tested by the real machine1) First, get the certificate and mobileprovision fileThe certificate needs double-click, enter the password for the certificate, and then import the tools under the Mac, such as:
2) Open the project and import the certificatehit the project name of the list on the left of Xcode, display the following interface, we choose targets under the xxx IOS, find code Signing under the code Signing Identity
on the first step, set active scheme to iOS Device, just select it to packageThe fourth step is to importmobileprovisionThe fifth step is to import the certificate,after 2 steps above, we open the general in, as shown in
1, is the package name2, the team that holds the Enterprise certificate3, is the name of the mobileprovision 4. The package name corresponding to the certificatethe problem is in the 4th step, the certificate and the package name does not match, then, how to solve, if this enterprise certificate is yours, then the point fix issue re-signed a certificate is good, if not, then can only re-create the project. 3) Re-create the package name corresponding to the certificate project, repeat 1) and 2)Open the general to find the package name again is not correct, because Xcode uses the package name is a dynamic variable assigned to the value, so we directly modify it (do not know the last step directly modify the package name is not good, have not tried, interested can try). This time, you need to open the information corresponding to the page, directly modify the bundle identifier content can be
may only need to modify the back of the can, however, I use, the default there is a-ios gray, so need to modify the bundle identifier, do not encounter this problem can not be used, if not understand the reference here. After you have modified the package name and the import certificate, you are finished with it, so start packing! 4) Modify edit scheme for release
1. Select Edit Scheme, and select iOS Device on the back platform2. Build configuration is release5) Select product->archive (if necessary, you can clean the project)The next step is the lengthy compilation process, which may also encounter unsupported arm64 solutions, with some error codes as follows:

Undefined Symbols for Architecture arm64:          ' _webpgetfeaturesinternal ', referenced from:              webpgetfeatures ( unsigned char const*, unsigned long, webpbitstreamfeatures*) in Libcocos2dx ios.a (CCIMAGE-5287FE6734B2FA44.O)          "_ Webpinitdecoderconfiginternal ", referenced from:              webpinitdecoderconfig (webpdecoderconfig*) in Libcocos2dx iOS.a (CCIMAGE-5287FE6734B2FA44.O)          " _png_get_io_ptr ", referenced from:

The workaround is to open the project directory, locate the cocos2d/external, search for _arm64.a files in this directory, and then drag the files you have searched to the frameworks of the Xcode project directory, and the dialog box pops up to select copy items if Needed and create groups two options, refer to Here6) Re-clean Execution archiveif it goes well, Xcode has helped us generate the following xxx.xcarchive file, or that sentence, if you are the Enterprise Certificate holder or team member, choose Export directly, if not, then only find another way. Cocoschina found a method, I just follow this method to do, so, not sure whether this method is useful.

This page can also be found through the window->organizer of the Xcode title bar. , you can see our xxx.xcarchive file, you can choose Export Exports IPA, which requires re-certification the practice on Cocoschina is:1. Right-click the generated archive file, which is the file under "name", select Show in Finder2, right click Xxx.xcarchive file, display package content, find the real Xxx.app3. Drag Xxx.app to itunes and the IPA file will be generated in the itunes directory4. In itunes, right-click on the xxx.app that we dragged in, show in Finder, find the generated IPA file. 3. Summarythe feasibility of the above method because there is no real machine test, temporarily can not be confirmed, but step 1-5 is a summary of the online tutorial. References:1) http://blog.csdn.net/yuxikuo_1/article/details/412788572) http://blog.csdn.net/justinjing0612/article/details/87586923) http://www.58player.com/blog-2527-123901.html4) http://www.cocoachina.com/bbs/read.php?tid=234530
I rookie one, the above method may not be formal, only to summarize the learning process records. If there is a better way, welcome to communicate.

Use XCode6.0.1 to package the cocos2d-x3.1 project with IPA (support iOS8)