IOS joins the corporate developer team for real-computer testing

found that most of the blog is about private real-computer testing methods, did not find a specific company team to develop a real-machine test method.

And from this week to leave iOS application software development, into the game development industry, today can remember the iOS knowledge will be forgotten, so Skipop still summed up one to give their own memo:

1. Usually use the company's mailbox to apply for AppID, and then let the company iOS team has permissions to the administrator to join the company's developer team.

2. Your company email will receive an invitation email from Apple and accept it.

3. Inform the company administrator of their real device number and let the administrator add this device to the list of devices on the developer team.

4. Generate a file with your Mac Keychain program (build steps many blogs have introduced, not detailed here).

5. On the Apple website login AppID, go to the developer team backstage, upload the files generated in the previous step.

6. Contact your company administrator to agree to your upload. By this step, your own registration is almost complete.

7. Download the company's project certificate to your Mac computer (it seems that the project certificate is the one that needs to contain the information of your real machine device).

The certificate section is almost complete, then configure your own computer:

8. add your own AppID information in Xcode--perferences---account (this is not required, you can replace it with other steps, but the next step will be convenient).

9. Open the company's project, connect to the real machine, set the code signing identify for its own certificate identification (with optional).

10. set iOS deployment target to the Phone SDK version in the project settings before you can find your mobile phone in the project running device (it looks like the Mobile SDK version is higher than the iOS deployment target version).

11. In the project Setup , set provision profile as the company-specific development version (there are generally multiple options, specifically, which one to ask the company team to know). At the same time, set the bundle identity to be consistent with this version (some companies have the option to include a category of "xxx.*", when using this version of the bundle identity can be set arbitrarily).