title: Managing Distribution Certificates with a Large Dev Team
body: <p>I am part of a development team with many apps spanning multiple business units and iOS teams.  We are having a lot of trouble right now managing distribution certificates.  Apple lets you have 3 distrution certificates on one development account, but there is no way to ﻿name﻿ the certificates uniquely, so they all look the same.  The only identifying information on the different certificates is the ﻿date﻿ on which it was generated.
  Apple, why can't we rename these distribution certificates so that we can manage them better???</p>
  
  <p>We need the ability to allow multiple build boxes to archive and submit to iTunesConnect for TestFlight or App Store releases.</p>
  
  <p>We are finding ourselves accidentally revoking each other's distribution certificates all of the time, and even worse making it impossible for beta users to install from TestFlight if the certificate has been revoked.
  Apple, why do you disallow installation of TestFlight builds if the "developer's certificate is no longer valid"???  This is crazy.  You don't do this when an app has been published in the App Store.  Why should TestFlight be any different???  Why punish beta users because the developers have accidentallly revoked a certificate???
  We also think that it is Xcode's "Reset" or "Fix it" buttons that are doing the certificate revoking and causing so much trouble.</p>
  
  <p>So how are other large development organizations handling this better?  We've got a big team, but not nearly as big as many others that are out there.</p>
  
  <p>We've tried assigning different dev teams a certificate generated on a particular date and asking them to only use that date and never revoke anyone elses' certificate.  We've also tried exporting certificates from a single box.  But it seams that no matter what we do something happens that causes the certificates to become revoked.  It seems that Xcode itself is causing this.</p>