About Apple iOS development, the author also from the small white come over, experienced various difficulties and pits, which have about development certificate, production certificate, In_house certificate, ADD_HOC certificate application process problems, as well as on-shelf issue. Focus today on the real-computer debug certificate request for updates to the Apple developer site.
All of these prerequisites are: you have to have an Apple Developer account ($), a company ($), a business ($299) account.
Start by opening the Apple Developer site (tips: I won't post the URL here)
Click member Center above the site to jump to the login screen (Tips: If you have logged in and selected the browser to save this password, the default is the login status).
Enter your developer account and password.
Click "Login" after the input is completed (Tips: The left is registered, below is the password, the right is login, if there is no developer account, you need to use the Apple account to apply for developers, there is not much to say the application process and recovery process).
After the login interface, if there is no top two options (Dev Centers, certificates,identifiers&profiles), you are currently logged in the account is not a developer, need a developer account login to have.
If the interface is the same as me, congratulations you can perform real-machine debugging, as well as publishing certificate operations.
First click on "Certificates,identifiers&profiles" to enter the certificate interface
We'll see four options under IOS Apps on the left: "Certificates", "Identifiers", "Devices", "Provisioning Profiles" (Tips: If this option is not available or is empty, It means that the developer account is not developed for iOS mobile app, for example, the current demo developer account is used for iOS development, so the middle of the Mac apps is empty, the module is selected in the Developer account application, this is not too much to repeat.
I'm going to show you the "IOS Apps" here.
First click on "IOS Apps" under the first "certificates", this option function as I understand is to authorize a computer to allow the real-time debugging (this is for everyone to understand, not too serious).
After entering the interface, the left column is the specific directory of the four options we just saw on the previous page, the right is the corresponding directory "certificates" under the "all" inside the specific content, the current directory is the authorization certificate, we look to the right there is a list of names called Type,type certificate type, For example, the "iOS Distribution" release authorization certificate, the "iOS Development" Debug License Certificate, the "APNs development ios" Push Debug License Certificate, etc., are now visible.
Click on the corresponding certificate will appear certificate details, there are removal and download options, here we click on the top right of the "ten" to create an authorization certificate.
After that we will see the interface, where we select "Development" under "IOS App development" for the real-computer commissioning of the PC authorization request. Then pull the interface down and click "Continue" at the bottom of the interface to create it.
This step, we continue to click on "Continue". This step is to say, need the computer keychain configuration file, I will tell you later, so we first click "Continue" to enter the next step.
This step requires us to upload the keychain configuration file.
OK, we now open our launchpad, find "Keychain access", open, do not wait for the interface to come out, directly in the upper navigation bar Select the "Keychain Access" directory under "certificate Assistant", select "Request a certificate from a certification authority."
If you want to receive a certificate by mail, you need to fill out the mailbox, two mailboxes filled in the same line, and then in the "request is:" Inside the "email to ca", you can receive the keychain profile by e-mail.
Here the author of the most simple and rough way to get the keychain configuration file, directly through the "request is:" Select "Storage to Disk", the above mailbox can be filled out (is required, but do not need to get through the mailbox, so just fill in the good).
Click Continue, we choose a location for our files, here I chose the desktop, of course, you must choose the location you can find.
We found our Keychain authorization file on the desktop. (Tips: Generated keychain profile is our current computer, that is, the current computer licensing real-world development, if you need to authorize other computers, you need the corresponding Keychain profile on other computers)
After we go back to the browser, we just need to upload the place, click "Choose File", find the place where we just placed the keychain configuration file. When selected, click "Open" and click "Generate" to generate our authorization certificate.
After the build, we will jump to the Download interface, click "Download" in the interface to download, download location must be found on their own.
Double-click the. cer file that we generated, make sure you double-click it, and it will be installed by default in the keychain, otherwise the problem will occur when you use it.
So far, we have completed the authorization of the current computer to allow the current computer for Real machine development (Tips: That is, the keychain has installed an authorization certificate, if it is used by the other computer keychain configuration file, you need to download the CER file, to the corresponding computer, and on the corresponding computer double-click).
We have finished the first step, then click on the left directory "Identifiers" under the "App IDs", here is to create a logo for our project, which is commonly known as signature, only the project to meet the mark to perform the real machine debugging.
Also click on the "Ten" button at the top right to create the logo.
Here, we need to create a logo, in the "name" where the name of the names, convenient for the final step to generate the certificate, it is easy to find the logo we created.
Next in the "app ID Suffix" in the "Explicit app id" "Bundle ID:" Fill in our logo (that is, signature), the format given below is an example. It's better to follow the format. The author's habit is like to put the company's web site anti-write finally add the project name, for example: Com.baidu.ZYBaiduExpPro.
Of course, we don't have to generate a signature for every project, and Apple provides us with a wide-area marking method.
is also the same interface, we choose "app ID Suffix" in the "Wildcard app id" inside the "Bundle ID:" Fill in our signature, note the format given below is an example. Here the author is also in accordance with this format to write, is still "com.baidu.*", when using the "*" to replace the various characters you need to line. That is, a wide-area indicator can correspond to multiple projects. After
We click on the bottom "continue" to proceed to the next step.
After checking the information, then directly click on the bottom "Submit" To publish the logo we created.
In this step, our logo has been created.
After we have authorized the computer to set the signature, we need to add the device, which is the device that allows the real machine to be debugged, for example (IPhone, ipad, etc.).
Click "Devices" in the left-hand directory and click on the "Ten" in the top right to add it.
We can choose to add one device at a time, or you can add multiple devices at once. The author is more respected is a one-time plus no trouble, one time to add multiple file format error-prone.
In the "Register device" inside the "name" to fill in the device name, in the future connected to the corresponding device, will be displayed in Xcode in the name.
Then, in the "UDID" filled with the device UDID, the process, need to get through the phone or itunes, here the author through itunes to obtain, because itunes comes with a copy.
Connected to the real machine debugging device, open itunes, click on the device, click the serial number in the interface, will switch to Udid, right click on the copy, copy it directly to paste it.
After clicking the "Done" button at the bottom of the interface, the device is added.
Only the last step is left to generate a debug certificate.
Click on the leftmost table of contents and select "All" in the "Provisioning Profiles" directory, and also click on the "Ten" in the top right to enter the certificate Add screen.
We select "IOS App development" and click "Continue" at the bottom of the screen.
This step is to choose the representation (or signature) we created, select the "Identifiers" we created in the 13th step, we must choose the right, if the creation of more than the marked, can be based on the name we created to find our logo,.
Click "Continue" to proceed to the next step.
This step is to choose our authorized computer, in the following options to choose our 11th step to generate the name of the authorization certificate, in this author to say one more, one but the creation of more than the certificate is not easy to find, can be based on the expiration date of the certificate created to distinguish, or remove the other (caution).
Click "Continue" to proceed to the next step.
This step is to choose the device we need to debug the real machine, you can choose our 14th step to create a designated device, you can choose all to see what you need.
Click "Continue" to proceed to the next step
For our certificate to choose a name, be sure to choose a good name, or later in Xcode will have a lot of certificates, not easy to find. Of course, when confronted with the development of many people, I tend to start with a, no matter how many certificates, always in front row.
Then click "Generate" to generate our final certificate.
In the new interface click "Download", download the certificate is our final certificate, still need to double-click, this double-click is installed to Xcode.
All right, here we have our certificate and we have finished our application. We downloaded a total of 2 files, one suffix is ". cer" files, and one is a file with the suffix ". Mobileprovision".
All right, now what's left? Is the commissioning of the real machine.
First open your project and select the project name under the "Supporting Files" directory under the project directory. plist file or "Info.plist" File (Tips: In Xcode6.0 is the project name. plist,xcode6.0 above is info.plist). Change the "Bundle identifier" label inside to the mark we just applied for (13th step).
If the tests Test folder exists in the project, the info.plist of the test file is changed as well.
After that, open your project root directory, the same life blue file, in the middle of the first select "TARGET" under the project name of the file, on the right side of the lap select "Build Setting", and then find the "Code Signing" option, in the "Provisioning Profile "Inside Select our 19th step to create the certificate, found by name. Then modify the "Code Signing Identity" above "Provisioning profile" to select the authorization certificate we found through the certificate. All four options need to be modified.
To do this, go back to our narrow interface and select the project in project with a file with the same name.
Finally, the last step left, make sure the device is connected to the computer, and in the unlocked state, select "Run Device" next to Xcode run, find your device, select, run, wait to load it.
If the device is not found, there is "IOS device", which means the device is not connected, or the device is not enabled in itunes. If it is not enabled, click the Device option in the top window to locate the appliance and enable it.
Up to this point, our real Machine Debug certificate is finished.END