The latest version of iOS support 3 developer certificate and 3 Publisher certificate, if it is redundant 3 computer equipment to the real machine debugging, it is more troublesome (mobile phone support 100 devices)
The solution is:
To install successfully on someone else's computer, you must have two files:
If you need to use it for development, these two files are required:
The. p12 file itself is an encrypted certificate, so you can use these two files to make other Mac devices available:
After you get these two files, double-click the "Certificates", ". P12" file (you need to enter the password, the password is the password that was generated when the. P12,), the role is to join the keychain, so that our computer has the proof of development, "profile" (role is placed in Xcode, Let Xcode know the legality of our development), after the addition can be used.
So if a new colleague joins the development team, you should select the certificate from the local keychain and export the P12 file (containing the certificate and key) to the colleague. You can also give a colleague a copy of the provisioning profiles file (config file) for locally developed identification test equipment (3 files)
In fact, these are the old way, the new version of Xcode is generally logged into the developer account, the relevant files will be automatically generated in Xcode, but if the third party, and do not want to let the other side know the secret, only need these original plan, is not let the other login account, to carry out the project development (tangle) In fact, there is a simple solution (by remote login, their own password, the other party does not know the password, so that the other party does not know the password, but also can play a safe role, more convenient, easier!!! )
https://ask.dcloud.net.cn/article/152
iOS personal developer account to other teams with the Pit Daddy tutorial