For iOS, Xcode automatically manages certificates, packages adhoc and testFlight for testing and installation, and xcodeadhoc

For iOS, Xcode automatically manages certificates, packages adhoc and testFlight for testing and installation, and xcodeadhoc

Introduction: IC manage signing is referenced after Xcode8. For developers, there must be many pitfalls in certificates.

Preparation: 1. the developer account is required.

2. Set the account in Xcode (do not tell Xcode your account, how to find your certificate and app Information)

3. Set the developer account in sequence. Briefly describe the specific settings.

From top to bottom, you must set the development certificate, app ID, model, and pp Certificate in sequence.

As you can understand, what is the purpose of Apple APP's developer account? It is to restrict development without money, publish APPs, and test on real machines.

However, these four things perfectly solve Apple's needs.

The first part (certificate) is the development environment certificate and production environment certificate. As the name suggests, it corresponds to the qualification requirements for development and release.

Part 2 (ID): Only the APP part. Create an app for your project bundle Identifier (Apple will certainly find your APP as a unique Identifier .)

Part 3 (device): Each mobile phone has a unique user ID (UDID ).

Part 4 (PP): follow the above three steps to create a certificate and your APP in the developer account, and register the mobile phone ID. However, there are multiple combinations of the three methods, each of which is a requirement. Therefore, PP files are files that combine the three methods.

 

Previously, Xcode manually selected the certificate and PP file, and both the PP file and certificate were created by itself. Now xcode can help you manage and create the file. For example, after you have created the development and production certificates, select adhoc during packaging, and Xcode will help you create an adhoc PP file.

 

The certificates and files created by xcode start with XC.

 

Page1: Package adhoc test ------- adhoc is actually a production environment without uploading the ipa package of the appStore.

① After selecting automatic management, the team selects your production environment certificate, and you don't have to worry about it. The rest is handed over to small X. ② Prepare the production environment. Set release in Edit scheme. ③ Select the product in the Xcode navigation bar and find archive. (If it is gray, it is not a real machine, or Generic iOS Device) ④ then wait. After packaging, export it and select adhoc storage. ⑤ In the installation section, double-click your packaged ipa package, open it in iTunes, and click Install .. Remember to remember to keep in mind the application in the lower right corner. Now we have done the page2: testFlight test. I like this test too. This is usually pre-installed before the release. General sales or many people test the release version, do not need to give the tester ipa package like adhoc, some problems may not stop, too much trouble. It is estimated that you can follow Apple's instructions in a few simple steps. ① First, you enter the developer account's iTunes connect and find your APP. ② There is testFlight in it. Select the APP you uploaded to iTunes connect and start the test. ③ Note: The tester should remember to add a selection in your account user, or else not send an email or test code to them. ④ With the test code, download the testflight APP and enter the test code to start the test.

Test advantage: Only upload the ipa package once without sending it back and forth.

When you upload a new version, an email is sent indicating that the new version can be directly updated.