When dealing with Apple, you'd better prepare a Mac. Here, you need to use a KeyAccess software that comes with Apple to generate a certificate application file.

After clicking "Apply for Certificate from Certificate Authority", the following figure will appear:

This is the e-mail address and name. Need to be reminded that we usually choose to "save" and store the application files on the hard disk. Later, we need to upload this file to Apple's backstage.

Apply for a certificate

After preparing the application documents for the certificate, it should be time to apply for the certificate.

Certificates are divided into development certificates and issuance certificates, and whether there is a push function or not is different. Select the certificate type according to the actual application function:

Then upload the CSR file just generated.

Click Generate, wait a moment, and the certificate will be generated. You can download and install it on this machine.

3.AppID

It should be emphasized that AppID and AppleID here are not the same concept. AppleID is the user's account in Apple, which is the account that needs to be used when downloading the application on the AppStore. AppID is the ID card of the application, which indicates the ID of the application.

After the certificate is generated, the next step is to generate AppID, which is equivalent to generating an ID card for the application you want to develop.

AppID needs a name for you to describe. You cannot enter special characters here.

AppID can also be divided into two types: with wildcards and without wildcards. When officially publishing an application on the AppStore, the application must have a unique name, so you need to use AppID without wildcards; At other times, in order to facilitate the use of multiple applications, we often use AppID with wildcards.

The last step is to choose the service of the application, which needs to be selected according to the actual situation of the application. If you don't know the specific situation of the application, then these options can be changed later, and you can choose the default.

Registered equipment

Because it is impossible for an Apple application to be released on the AppStore during the development process, such a half-baked application cannot be installed on the device. What about debugging and testing? Apple has launched the Adhoc version, which belongs to the pre-release beta. Only devices registered in the background and imported by signature files can be installed and run.

You need to enter the UDID of the device here. Depending on the account type, you can register 100 or more devices.

5. Generate a signature file

Signature file is the core file for applying signature. Signing files are also different from developing and publishing. Of course, the signature files published by Adhoc and AppStore are also different.

5. 1

The signature file needs to be bound to AppID. This signature file selected according to the actual situation will be bound with an AppID with wildcards, which can be used in a series of applications. To publish the signature file of the AppStore, you must bundle the AppID without wildcards.

5.2

Then select a certificate:

5.3 The next step is to select equipment. Only the selected devices can install applications. Of course, if it is the signature file of the AppStore, there is no such step.

5.4 Finally, enter the name of the signature file and press the Generate button to generate the signature file.

In this way, after generating a series of related contents, a signature file is generated. You can download this document and sign the application!

end