Certificates

Requires a paid Apple Developer Program membership (some capabilities are available to free accounts; see limitations below).

Certificates are used to sign apps. There is generally a limit of 3 certificates for the same type, and one certificate can be used by multiple apps. Push certificates are deployed on the push server for push notifications; they are not used to compile apps. Accounts that have not joined the Apple Developer Program only receive certificates with a validity period of 7 days.

Creating a Certificate

Use Appuploader to create a certificate:

1. Click “Create Certificate” and choose the certificate type (e.g., development signing certificate, distribution signing certificate, push certificate, etc.).
2. Select the identifier to bind (App ID / Pass Type ID / Merchant ID, depending on the certificate type). If there are no options, you must first create an identifier in the corresponding function (such as Bundle ID), and then return to issue the certificate.
3. Fill in a certificate name (so you can recognize it later in the list) and an email address.
4. Set a .p12 protection password. This password is used to encrypt the .p12 file that contains the private key. The server does not store this password. You will need to enter it when downloading or importing the certificate. Keep it safe; if you forget it, the private key cannot be used.
5. Optionally, check “Use the Kaixin service to sync the certificate” (cloud backup). After syncing, you can download the certificate on any computer. If unchecked, the certificate can only be downloaded on the current machine; for other computers, you must manually send and manage the certificate file.
6. After submission, the certificate is signed/issued by Apple.

Managing Certificates

• The list shows the name, type, status, and expiration time, and supports search by name/type/serial number.
• Cloud backup: You can make a cloud backup of an existing certificate at any time, and it will be synced to the Kaixin cloud.
• Download: When there is no local .p12 file, the system will try to download it from the cloud (provided a cloud backup was made previously).
• Revocation: Revoking the certificate from Apple’s portal is irreversible; after revocation, all provisioning profiles that depend on this certificate must be regenerated.