IOS Packaging Process

Once you have opened your app with Xcode, double-click the uploadtest.mobileprovision authorization file and it will install itself into Xcode.   then follow the instructions in the:   if the team does not have an option:    add your developer account, the team will have an option to name your account, select it. (There may be delays, may appear later)   NOTE: If you have two options in your account name, one is the development certificate, and the other is the publishing certificate. The development certificate will be followed by the word "(Personal Team)", and the other one is the publish certificate (packaged online).   Here we can start packing and uploading.    Open Product-> Archive Click    if Archive fails, there is no corresponding UUID found ... The wrong words (such as) the code Signing in the provisioning Profile selection automatic, re-archive can be   archive success will pop up a window such as, Click Validate to verify the app.       Click Validate Verify    Verify this step may be a bit time consuming (related to Apple server and your network)    verify success, click Upload to When App Store uploads    uploads app Stroe, be aware that the app ID is consistent with your xcode, and note that the issue with that version number;   the same as validate, select the team that corresponds to the development certificate , click choose   and then click upload button upload     upload may also be a bit time-consuming, can only wait for ...   upload success will have success reminders, click Done. At this point it has been stated that the package Upload App Store is successful    to itunes connect backstage-> Your App-> ready to submit Version-> the "+" sign next to the build version or choose a build.    Select the version that you just packaged and upload, click Finish.    here is to note that the. IPA package uploads successfully to the build version, this time is indeterminate, general wordsIt's about half an hour, but it could be a couple of hours, but it's over. Other information in the itunes Background app can be filled in according to the company's requirements, then click "Save" in the top right corner and click "Submit for Review".    above, if the company does not specifically specify, select No and then submit.    about the general concept of certificates:  1.    certification (certificate)
Certificate is the qualification of computer development certification, divided into two kinds:
1) Developer Certification (development certificate)
Install on the PC to provide permissions: The developer tests the device for real-world testing.
Copies can be generated for multiple computers to be installed;
2) Distribution Certification (release certificate)
Install on your PC to provide permission to publish iOS programs: Developers can make beta and release programs.
Copies can be generated for multiple computers to be installed and used;
Note: After the two certificates have been configured and downloaded using a computer's CSR file, only the computer that configured the certificate can be used. So if you want to use the above two types of certificates with other computers, you need to make a copy (that is, generate. 12 files) (The copy system is introduced in the following keychain)


2. Provisioning profile (Authorization document)
Authorization files are authorized for devices such as ipod Touch, IPad, iphone, the udid of the device and the app ID of the program, even if the authorized device can install or debug the bundle identifier program that corresponds to the app ID recorded in the authorization file.
The developer account will choose the app ID when creating the authorization file (add the app ID in the developer account, select a single) and Udid (add up to 100, multi-select in the developer account under devices).
The authorization file is divided into two types, corresponding to the corresponding certificate use:
1) Developer Provisioning profile (Development authorization file)
Used on a computer with a development certificate or a copy (. p12 file), the developer chooses the authorization file to install the program to a device in the authorization file record through the computer, and can perform a real-machine test.
Note: Make sure that the computer has permissions to debug, that is, the development certificate or copy is installed, the bundle identifier of the program in the development tool and the app ID of the selected authorization file are consistent; The udid of the device that connects the debugs is recorded in the selected authorization file.
2) Distribution Provisioning profile (Release authorization file)
The beta and release programs are made on a computer with a publishing certificate or a copy (. p12 file).
The release is the program file that is published to the App Store, and the developer account chooses the store option when creating the authorization file, choose the app Id, no need to select Udid;
The beta version is the program files that the tester can sync to the device before it is released, select Adhoc when creating the authorization file for the developer account, select the app ID and Udid, and only the selected Udid device may install the program that is made from that authorization file.
3. Keychain (Development key)
If the certificate is successfully installed, keychain will be generated under the certificate, and the copy of the certificate mentioned above is the computer that is configured with the certificate to export keychain (that is. p12 file) to the other machine, so that the other machines get the certificate corresponding permissions. Developer Certification and distribution certification can be made copies of keychain (i.e.. p12 files) distributed to other PCs to be installed so that they can be tested or published for real-world applications. The. p12 file exported by the distribution Certification certificate is installed on a different computer and can be given permission to publish apps to other computers. Export process for replicas (. p12 files): Locate the certificate that needs to be exported in Keychain Access-> Right-click-> select Export (Your certificate) Click Save to set a password for the. p12 file. Then locate the. p12 file in the storage Path v. Development of push and processing of production certificates About push development and production certificates: 1. Double-click to install the certificate (. cer) into keychain access; 2. Export the. p12 file according to the process of exporting. p12 files, 3. Pass the password on the. p12 file and file to the third-party push platform.

IOS Packaging Process