All iOS certificate and provisioning files that are part of the certificate set have an expiration date - in other words, are valid for a specified time, only. You can check the expiration dates for all the certificates that are defined in the Pega 7 Platform directly from the Certificates landing page - the Expires In column shows the next expiration date for each certificate set shown in the list.
When a given iOS certificate or provisioning profile expires, you need to either generate a new one or extend the time during when it is valid. Remember that it is important to always update the certificates before they expire for your applications. You always create a new certificate and provisioning file, or update its details, directly from the Apple Dev Member Center.
Certificate type |
Certificate expiration |
When certificate expires |
| Provisioning file | Typically expires after one year. | The application will start on devices where it has been already installed. However, you will not be able to install it on new devices. |
| Signing | Typically expires after either two or three years. | The most serious case. The application will not start on new devices the application was installed, as well as on devices where it has already been installed. |
| Push notification (APNs) | Typically expires after one year. | Push notifications will not be delivered. |
When you update a provisioning file or a signing certificate, you need to rebuild and install the application on each device. When you update a push notification (APNs) certificate, you need to just update the new certificate set in the Pega 7 Platform. In such a case, you might need to sign in to the application again, on each device.
When you edit a certificate set or update a file which will expire, you cannot change the App ID (Bundle ID). Remember that when you are updating a certificate, you must always create it for an already existing App ID. You can only update a certificate for an existing App ID.
You only update the provisioning file, or only update the push notification (APNs) certificate on its own. However, keep in mind that when you update a signing certificate, you will also need to update the provisioning file to which it relates.