Previously this book has discussed how we would automate and manage the process of creating certificates and provisioning profiles, and subsequently, code signing through public/private keys (separately, for both development and distribution). We discussed the theory and processes for working with profiles and certificates in great detail, and while fastlane has done a great job in allowing developers to not only manage but also repair their code signing assets with sigh and cert, there is one glaring problem—each developer still has an individual profile, and that leads to numerous profiles.
The number of profiles will grow as the teams grow, and, even with personnel leaving, they have to be pruned over time; needless to say, it's a model that isn't exactly scalable. Each new machine will require quite a bit of setting up using individual...
