iOS device debugging process of opening

update record

time	Modified version
2020 March 29	First draft

Foreword

• Recently, due to the re-installation of the operating system mac, need to re-open a real machine debugging.
• Opening device debugging, run the process again when there are still no links stroke clear (because there are some aspects, the applicant did not distinguish between good in the end is doing, or administrator to do), then went to ask the head.
• As the head last time and I have introduced a whole process, and I forgot (and did not do their summary and notes), ask again. So I feel ashamed.
• I propose that on this record, summarize iOS device debugging (Enterprise Edition) opening process. (Personal Edition device debugging should be similar)

Open process (divided into 6 steps)

1. Join the Developer account team (applicant and co-operation administrator)
   • To find the administrator logged on with administrator privileges, belonging to the team's account, send e-mail to the applicant an invitation to join
   • Applicants receiving mail, was added to the team
   • Explanation: This step is focused on, is confirmed apple id
2. Add test machine identifier (administrator operations)
   • Need to find the real machine debugging Apple phone identifier (referred to herein as iPhone ID)
   • Administrator to increase the iPhone IDlist of machines to developer account (which allows real machine ID list Device Debugging)
   • Explanation: This step is focused on, is to confirm device id
3. Certificates application (Applicant operation)
   • xcode-> preferences-> accounts (own that joined the team of the apple id) -> manager certificates
   • Click the plus sign to create a signing certificates (and will upload a public key to Apple background)
   • Explanation: This step is focused on, it is to confirm the mac computer. (Id similar effects, mac essentially a computer-generated public and private key for the RSA)
4. Update Provisioning Profiles (administrator operations)
   • Select the current developmentprovisioning profiles
   • Edit select all developers certificates and devices
   • Click Generate, generatedProvisioning Profiles
   • Explanation: This time, Apple has been the background of the public key mac computers (PCs confirm identity), developer apple id list (to confirm the identity of the developer), device id list (to confirm the identity of the Apple phone).
     • In fact, here on the site, as well as corresponding to different app target, there is a corresponding app id (confirmed as app). Therefore, the generated Provisioning Profilescontains a confirmation mac computers, developers, Apple phone, app identity of the four.
5. Xcode download Provisioning Profiles (applicant's operation)
   • xcode-> preferences-> accounts, click Download Manual Profiles, complete download.
6. verification
   • Open the Xcode project settings, find Signing (Debug)
   • Provisioning ProfilesfillAppStoreDevelopment
   • Team will automatically become the actual team
   • No other red warning or error, indicating that the target already has a device debugging permissions.

to sum up

• Seen from the above steps, device debugging need to verify mac computers, developers, Apple phone, application identity of the four, it can be a real machine debugging.

The words written on the back

• The article made reference to the head of a colleague guidance articles and articles on-device debugging verification process, but because of articles posted it for the articles within the company, so not posted links.
• Follow-up plan to write an article on the principle of iOS-device debugging process, this article only for reference, how to open device debugging permissions (that I do not care why, just tell me how we can open device debugging permissions)
• In fact, there's little I never understood:
  • For several target (ie, a few app id) of the id, whether it is all stored in the same one Provisioning Profilesin?
  • If not, it is necessary to step 5 several times it?
  • The question for managers, should know better. Subsequent re-issue the update.