IOS study tip 20: Archive and package applications and test and upload distribution to App Store

Distribution and upload of IOS apps.

There are two main steps: first, enter the developer account to apply for and layout A new application material in iTunes connect; second, archive, package, and upload

I. Apply for and layout A new application on iTunes connect

1. Prepare one image resource: the large app icon seems to be 1024*1024 (this is prompted); 1-5 images. (If your app is compatible with the iPhone 5, you need a 4-inch screen)

2. Go to iTunes connect ---> Manage Your applicationsg to create an app based on the corresponding steps. It is basically no difficulty to fill in the information according to the steps.

3. If you are preparing to upload an object, set the application status to waiting for upload.

Ii. Archive and Package

1. Before proceeding to this step, we hope that the distribution certificate and the Distribution distribution description file will be generated and installed.

Certificates manages your two certificates: development and distribution. Similarly, different types of certificates also manage different description files.

Two delivery description files are attached to the Distribution Certificate, one for appstore upload and the other for ad hoc share.

This is the corresponding development and distribution description file.

2. After downloading and installing the description file, you can archive and package it in xcode.

Modify the configuration in xcode:

1> change bundle identifier to the appid specified in your description file.

2> set code signing... and release to select your Distribution Certificate. (Change both the project and target ).

Of course, you 'd better first edit scheme to ensure that your archive build method is release (usually the default is ).

3> archive. Before that, change the device link to iOS device. If the selected device is a simulator or something, the red option is gray.

4> You will access your private key signature in the middle, and then directly jump to the archive option on the organize interface.

There are two buttons on the right. The first one is used for verification.

Verify that the app you want to upload meets your record on iTunes connect

(For example, after uploading, you click this button to display

).

Select the distribution option first.

The third step is to export an archive file. If you are not clear about its usage, you will feel like sending it to other colleagues who can directly view it in this option.

Then, you can use his existing certificate signature for verification. If yes, he can also upload and distribute the signature, but it is only a step less archiving.

The second is to generate an ad hoc Type Distributed IPA and then send it to the description file for installation and use of the device.

The first one is submitted to the app store.

TIPS:

1. Remove nslog when the application is published and add a macro to the pre-processing XXX-Prefix.pch

// Log # ifdef debug # else # define nslog (...) {}; # endif

2. When I pack and publish an ad hoc file, I find that you do not need to publish a certificate. You can archive and package the file directly with the developer certificate. Some signing steps are gone, but the application can still be installed on the device (

In the beginning, I didn't pay attention to using the development certificate archive to directly install it through iTunes ).

The basic process of archiving and packaging is simple. Still relatively simple