1 First, open Apple's developer website, and click MemberCenter at the top of the website to jump to the login interface. 2. As shown, enter the developer account and password. 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). 3. The login interface is shown in the figure below. Without the first two options (development center, certificate, identifier &; Profiles), indicating that the currently logged-in account is not a developer, and you need a developer account to log in. 4. First click Certificate, Identifier &; Profiles ",when entering the certificate interface, you will see four options under iOSApps on the left: certificate, identifier, device and ProvisioningProfiles" (Tips: if this option is unavailable or empty, it means that the developer account is not developed for iOSApps) 5. Click the first certificate under IOSAPPS. After entering the interface, the left column is the specific directory of the four options just seen on the previous page, and the right column is the specific content in "All" under the corresponding directory "Certificate". The current directory is an authorization certificate with a column named Type on the right. Click on the corresponding certificate to display the details of the certificate, with options of removing and downloading. Click "10" in the upper right corner to create an authorization certificate. 6. After that, you will see the interface as shown in the figure. Select "iosapp Development" under "Development" and apply for computer authorization to debug the real machine. Then drop down the interface and click "Continue" at the bottom of the interface to create it. 7. In this step, continue to click "Continue". This step means that if you need a computer keychain configuration file, click "Continue" first to enter the next step. 8. In this step, you need to upload the configuration file of keychain. Open Launchpad and find keychain access. After opening, you don't have to wait for the interface to come out. You can directly select the certificate assistant under the Keychain Access Directory in the navigation bar above, and choose to apply for a certificate from a certificate authority. As shown in figure 9. If you want to receive the certificate by email, you need to fill in the email box, just fill in two emails, and then select "Email to CA" in "Request Yes" to receive the keychain profile by email. Select "Save to Disk" directly in "Request Yes", and you can fill in the above email address at will (required, but you don't need to get it through the email address, just fill it in at will). Click Continue and choose a location for the file. Here I choose the desktop. Of course, I must choose the place where I can find it. 10. Find the keychain authorization file on the desktop, as shown. (Tips: The generated keychain configuration file belongs to the current computer, that is, the current computer is authorized to develop real machines. If you need to authorize other computers, you need the corresponding keychain configuration file on other computers.). Then, go back to the browser, click "Select File" where you just need to upload, and find the place where you just put the keychain configuration file. After it is selected, click "Open" and "Generate" to generate the authorization certificate. 1 1. After it is generated, it will jump to the download interface, click "Download" in the interface to download, and the download location must be found by yourself. Double-click the generated. Cer file, be sure to double-click it. After double-clicking, it will be installed in the key chain by default, otherwise there will be problems when using it. So far, the authorization of the current computer has been completed, allowing the current computer to develop a real computer (Tips: the key chain has installed the authorization certificate. If you are using the keychain configuration file of another computer, you need to download the cer file to the corresponding computer and double-click on the corresponding computer. 12. Then click "AppIDs" under "Identifiers" in the directory on the left. This is to create a logo for the project, also known as the 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. 13. Here, you need to create a label. Fill in the name of the label at "Name" so that the created label can be easily found when the certificate is generated in the last step. Next, fill in my tag (i.e. signature) in "BundleID:" of "ExplicitAppID" in "AppIDSuffix", and an example is given below. Just follow the format. Of course, it is not necessary to generate a signature label for each project. Apple provides a wide-area labeling method. In the same interface, select "BundleID:" in "WildcardAppID" in "AppIDSuffix" to fill in the signature, and pay attention to the example given below. Then click "Continue" at the bottom to go to the next step. After checking the information, click "Submit" at the bottom to publish the created logo. At this point, the logo has been created. 14. Computer authorization. After setting the signature, you need to add equipment, that is, equipment that allows 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. Choose to add one device at a time, or add multiple devices at a time. Fill in the device Name with "name" in "RegisterDevice", 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. 15. Click the leftmost directory column, select "All" under the "ProvisioningProfiles" directory, and click "Ten" at the upper right to enter the interface for adding certificates. As shown in the figure. Select "iOSAppDevelopment" and click "Continue" at the bottom of the interface. 16. This step is to select the created representation (or signature). Select the Identifier created in step 13, and make sure to select the correct identifier. If a lot of tags are created, you can find the tags according to the created names, and click "Continue" to continue to the next step. 17. This step is to authorize the computer. Select the name of the authorization certificate generated in step 1 1 from the following options. Once more certificates are created, it is difficult to find them. You can distinguish the certificates created by their expiration dates, or delete other certificates (note). Click "Continue" to proceed to the next step. 18. This step is to select the equipment that needs real machine debugging. You can choose the specified equipment created in step 14, or you can choose all of them to meet your needs. Click "Continue" to go to the next step 19. Choose a name for the certificate, be sure to choose a name that is easy to find, otherwise there will be many certificates in Xcode in the future, which is not easy to find. Then click "Generate" to generate the final certificate. Click "Download" in the new interface, and the downloaded certificate is the final certificate. You still need to double click. This time, double-click to install to Xcode. Ok, the certificate application is over. A * * * downloaded two files, one with the suffix ". Cer "and another with suffix". Mobile supply ". 20. Ok, now let's debug the real machine. First, open the project and select the project name. Plist file or "info.plist" file in the "SupportingFiles" directory under the project directory (hint: it is the name of the project. Plist below Xcode6.0, info.plist above Xcode6.0). Modify the label "Bundleidentifier" to the label just applied (in step 13). After 2 1., open the project root directory and the blue file with the same name. First, select the project file with the same name under "TARGET" in the middle, select "building setting" on the rightmost overlapping surface, then find the option of "coding signing", select the certificate created in step 19 in "ProvisioningProfile" and search by name. Then modify the "CodeSigningIdentity" on the "ProvisioningProfile" to select the authorization certificate found by the certificate. All four options need to be modified. After completing this step, return to the narrow interface in the middle, and select the project file with the same name in Project to do the above operation. 22. Finally, there is only one last step left. Make sure that the device is connected to the digital computer. In the unlocked state, select "Run Device" next to Xcode Run, as shown in the figure. Find your own device, select, run and wait for loading. If the device can't be found and there is an "IOSDevice", it means that the device is not connected correctly, or the device is not enabled in Itunes. If not, click Device Options in the top window to locate the device and enable it.