1

First, open Apple's developer website (Tips: No URL posted here).

Click the Member Center at the top of the website to jump to the login interface (Tips: If you have logged in and selected a browser to save this password, it will be logged in by default).

2

Enter your developer account and password as shown in the figure.

Click "Login" after entering (Tips: register on the left, retrieve the password below, and log in on the right. If there is no developer account, developers who need to apply for an Apple account will not say much about the application process and retrieval process here).

three

The interface after login is shown in the figure. Without the first two options (development center, certificate, identifier &; Profiles), indicating that your current login account is not a developer, and you need a developer account to log in.

If the interface is the same as mine, congratulations on debugging the real machine and issuing the certificate.

four

Click Certificate, Identifier &; Personal data ",enter the certificate interface.

We will see that there are four options under "iOS Application" on the left: Certificate, Identifier, Device and Preset Profile (Tips: If this option is not available or empty, the developer account is not developed for iOS mobile application. For example, the developer account currently demonstrated is used for iOS development, so the Mac application in the middle is empty.

Here I use the "iOS app" to show you.

First, click the first "Certificate" under "iOS App". As far as I know, the function of this option is to authorize a computer to debug the real machine (this is just for everyone's understanding, so don't be too serious).

After entering the interface, the left column is the specific directory of the four options we just saw on the previous page, and the right column is the specific content in the "All" under the corresponding directory "Certificate". The current directory is an authorization certificate. We see that there is a column named Type on the right, which indicates the types of certificates, such as "iOS distribution" publishing authorization certificate, "iOS development" debugging authorization certificate, and "APNs developing iOS".

Click the corresponding certificate, and the certificate details will appear. There are deletion and download options. Here, we click the "ten" in the upper right corner to create an authorization certificate.

After that, we will see the interface as shown in the figure. Select "iOS App Development" under "Development" here to apply for the authorization of debugging the real computer. Then drop down the interface and click "Continue" at the bottom of the interface to create it.

At this step, we continue to click "Continue". This step means that you need a computer keychain configuration file, which I will tell you later, so let's click "Continue" and go to the next step.

This step requires us to upload the configuration file of the keychain.

Ok, let's open our startup board and find the keychain to visit. After opening, we don't have to wait for the interface to come out. We can directly select "Certificate Assistant" in the Keychain Access directory in the navigation bar above, and then select "Apply for a certificate from a certificate authority". As shown in the figure:

If you want to receive the certificate by email, you need to fill in the email boxes, just fill in two email boxes, and then select "Email to CA" in "Request Yes" to receive the keychain profile by email.

Here, the author uses the simplest and rudest way to obtain the key chain configuration file, and directly selects "Save to Disk" in "Request Yes", and the above email address can be filled in casually (required, but not necessarily obtained through email, just fill in casually).

Click "Continue" and we will select a location for the file. Here, I will choose the desktop. Of course, I must choose the place where I can find it.

We found our keychain authorization file on the desktop, as shown in the figure. (Tips: The generated keychain configuration file belongs to our current computer, that is, the current computer is authorized for real machine development. If another computer needs authorization, it needs the corresponding keychain configuration file on the other computer. )

Then we go back to the browser, where we just need to upload, click "Select File" and find the place where we just put the keychain configuration file. After selecting, click "Open" and "Generate" to generate our authorization certificate.

After it is generated, we will jump to the download interface and click "Download" in the interface to download. You must find the download location yourself.

Double click. The cer file we generated. Please be sure to double-click. After double-clicking, it will be installed in the key chain by default, otherwise there will be problems when using it.

So far, we have authorized the current computer, allowing the current computer to develop a real computer (Tips: Keychain has installed an authorization certificate. If you use another computer's keychain configuration file, you need to download the cer file, give it to the corresponding computer, and double-click on the corresponding computer.

We have finished the first step, and then click "Application id" under "Identifier" in the directory on the left. Here is to create a logo for our project, which is also commonly known as signature. Only the items that meet the logo can be debugged on the real machine.

Similarly, click the "Ten" button in the upper right corner to create a label. As shown in the figure.

Here we need to create a logo, and fill in the name of the logo at the "name", so that when the certificate is generated in the last step, it is easy to find the logo we created.

Next, fill in our logo (that is, signature) in "Bundle ID:" of "explicit App ID:" in "App ID suffix", and the format is given as an example below. Just follow the format. The author's habit is to write the company website backwards and add the project name at the end, for example: com.baidu.ZYBaiduExpPro

Of course, we don't need to generate a signature label for each project. Apple provides us with a wide-area labeling method.

On the same interface, we select "Bundle ID:" in "wildcard application ID" in "application ID suffix" to fill in our signature, and pay attention to the example given below. The author here also wrote in this format, or "com.baidu.*". When using, just replace the "*" with all the characters you need. In other words, a wide-area sign can correspond to multiple items. As shown in the figure.

Then, we click "Continue" at the bottom to go to the next step.

After checking the information, click "Submit" at the bottom to publish the logo we created.

At this point, our logo has been created.

After we authorize the computer to set the signature, we need to add devices, that is, devices that allow real machine debugging, such as (iPhone, ipad, etc. ).

Click "Equipment" in the directory on the left, and click "Ten" at the top right to add.

We can choose to add one device at a time or add multiple devices at a time. The author argues that adding one file at a time is not troublesome, and adding multiple file formats at a time is prone to errors.

Fill in the device name with "Name" in "Register Device", and this name will be displayed in Xcode after connecting the corresponding device in the future.

After that, fill in the UDID of the device in "UDID". This process needs to be obtained through mobile phone or ITunes. Here, the author got it through ITunes, because ITunes has its own copy.

Connect the device to be debugged by the real machine, open ITunes, click the device, and click the serial number in the interface to switch to UDID. Right click to have a copy, just copy and paste it directly.

Then click the "Finish" button at the bottom of the interface to finish adding the equipment.

Only the last step is left, and the debugging certificate is generated.