IOS InHouse Release Process

There are two types of IOS certificates.

The first is $ $, this account has a personal and company differences, the company account can create multiple sub-accounts, but the individual can not. This account can be used to upload the App Store

The second is $299 for ￥, an account that can only be used for internal use and cannot be used to upload the App Store. That is, the in-house certificate (a package with this certificate can be run on any iOS device without the need for Apple authentication, Signature)-Don't misunderstand the ability to upload an App store with in-house. These are two different accounts.

Develop the required certificates for iOS

Certificates for. CER types

When this certificate is created, you will be asked to choose a local private certificate to upload. is also required for development of the certificate, you can choose to bind the appropriate app IDs

. P12 a similar certificate

If a developer account is used by more than one person, the certificate will be directed from the local keychain access to the above. CER certificate. Then select the suffix named P12.

. mobileprovision file

It will add all the devices in the developer account when it is created. Only Xcode has this file installed to debug (note. If the mobileprovision here is distribution then it cannot be tested on the real machine, only uploaded to the App Store through Apple's audit to properly install into the iOS device.

Generally speaking, as long as the above three kinds of certificate files, you can debug on the real machine. (Note that developer similar certificates can only be used for testing, and distribution certificates can only be used to upload apps that cannot be installed to iOS devices until they are online)

1. Log in to https://developer.apple.com and enter the iOS Developer Center. Create a certificate in Certificates-production.

2. Select in-house and Ad Hoc, click Continue. Note that if you have already created a in-house certificate, you can no longer create it, and the option will be dimmed, such as. If you want to recreate it, you can revoke the certificate in the previous list first.

3. Enter keychain access in the MAC system (you can search directly with Spotlight), select Keychain Access-Certificate assistant-Request a certificate from a certification authority.

4. Enter your email address and name and select "Save to Disk"

5. Upload the generated "certificatesigningrequest.certsigningrequest" file to the Developer center, click Next Build, then download the generated certificate locally and double click to open it. You can see in the keychain that the certificate has been successfully installed.

6. Go back to iOS Developer Center and create an app ID in "Identifiers"-"app IDs". I am creating the explicit app Id,wildcard app ID should also be OK.

7. In provisioning profiles, add a profile corresponding to the AppID you just created, select "In House"

8. Select the app ID you just created

9. After creating and generating profile, download to local, double click to open, add to library.

10. Open the project where you want to export the IPA, select the iOS Device in the scheme

11. Select Product-archive from the menu

12. In the pop-up Orgnizer, select the archive you just generated (selected by default), and then select Distribute in the upper-right corner.

13. Select save for Enterprise or Ad Hoc Deployment

14. Select the profile you just created

15. In the pop-up Save box, select "Save for Enterprise distribution" and fill in the IPA path on the server (the server address needs to be changed to its own) and the name of the app, choose Save Path, click "Save".

16. Next you will see the generated two files under the path you just saved, and we need to upload the two files to our server.

If you feel that you can help, but also hope to help the top, thank you:) Personal blog: http://blog.csdn.net/zhaoxy2850 This article address: http://blog.csdn.net/zhaoxy_thu/article/ details/17277527 Reprint Please specify the source, thank you!

IOS InHouse Release Process