I am part of a development team with many applications spanning multiple business units and iOS teams. We now have many problems managing distribution certificates. Apple allows you to have 3 certificates of permission per development account, but certificates cannot be unambiguously named, so they all look the same. The only identifying information about the different certificates is the date on which it was generated. Apple, why can't we rename these distribution certificates so that we can better manage them?
We need the ability to allow multiple build blocks to archive and send to iTunesConnect for the TestFlight or App Store editions.
We find that each time we randomly revoke distribution certificates one after another, and even worse make it impossible for beta users to install from TestFlight if the certificate was revoked. Apple, why do you prohibit the installation of TestFlight tests if the "developer certificate is no longer valid" ??? This is madness. You do not do this when the app was published on the App Store. Why should TestFlight be different? Why punish beta users because developers accidentally revoked a certificate ??? We also believe that these are the Xcode “Reset” or “Fix it” buttons that revoke the certificate and cause such a big problem.
So how do other large development organizations deal better with this? We have a large team, but not as large as the many others that are there.
We tried to assign a certificate generated on a specific date to other groups of developers and ask them to use only this date and never revoke a single elses certificate. We also tried to export certificates from one window. But it’s the seams that no matter what we do, something happens that causes the certificates to be revoked. Xcode itself seems to be causing this.
source
share