A while ago, our company launched a second app. When preparing to package it, I ran into a problem: an Apple developer account can create at most two distribution certificates, but our team had more than two products. Did every app need its own set of certificates? After checking Apple's backend documentation and asking colleagues, the conclusion was simple—multiple apps can use the same iOS certificate; what truly needs to be created per app is the provisioning profile. This article breaks down the relationship between certificates and apps, and then explains the boundaries of sharing.
Why can it be shared?
To understand why sharing is possible, you must first distinguish the responsibilities of certificates and provisioning profiles. A certificate answers "who signed it": it represents your developer identity, signs the app with your private key, and the developer name shown in the App Store comes from the certificate. A provisioning profile answers "which app can use it": it binds the certificate, App ID (Bundle ID), and test devices together. One provisioning profile corresponds to one App ID. Certificates manage identity, and provisioning profiles manage entitlement—so one certificate can sign multiple apps, as long as each app has its corresponding provisioning profile.
How to do it in practice
In practice, you only need to create the distribution certificate once: use Appuploader to create a distribution certificate (iOS Distribution) in certificate management, generate a P12 file, and securely store the private key password. Then, for each app, go through the provisioning profile process separately: create a new provisioning profile in Appuploader, select the type App Store (for distribution), and choose the corresponding Bundle ID. If you have multiple apps, create multiple provisioning profiles, each bound to its own App ID. When packaging, use each app's specific provisioning profile while sharing the same certificate—this works perfectly for uploading to the App Store.
A side note on quotas: Apple is relatively lenient with development certificates, but you can have at most two distribution certificates, and enterprise accounts have separate quotas. This is why many teams share a distribution certificate—not because they don't want to create a separate one for each app, but because the quota is limited. Sharing is actually the standard practice.
Boundaries for individual and company accounts
There are several boundaries to clarify when sharing certificates. For individual and company accounts, sharing a certificate within the same team is fine, but it is not recommended to send the certificate to people outside the team for building apps—if someone uses your certificate to build an app, the developer name shown in the App Store will be yours or your company's, and you will bear the responsibility if issues arise. Your intellectual property may also be at risk. Only share the certificate with trusted individuals; don't treat it as a public resource.
Boundaries for enterprise accounts
For enterprise accounts, you can technically share certificates with others for building, but restrictions are stricter: enterprise certificates are only allowed for internal distribution within the enterprise, not for App Store release or internet installation. If you distribute an enterprise-certified package externally, Apple may detect and revoke or ban the certificate, causing all installed apps on users' devices to lose their validity. This risk is much greater than with individual accounts—don't cross that line.
Provisioning profiles cannot be shared
Another common misconception: certificates can be shared, and the P12 private key can be synchronized across computers in Appuploader to facilitate team collaboration. However, provisioning profiles are not universal—every app must have its own provisioning profile. This is the first thing to check when you encounter "provisioning profile does not match certificate" errors during packaging.
In summary, using the same certificate for multiple apps is normal practice. Remember three points: certificates manage identity and can be shared; provisioning profiles manage entitlement and must be created per app; and your account type determines the extent to which certificates can be shared.
Top comments (0)