Manage Push Credentials

Push credentials are required to receive incoming call alerts on iOS and Android apps. The alert is delivered to devices using Push Notifications. Plivo Mobile SDKs integrates Apple Push Notification service (APNs) for iOS and Firebase Cloud Messaging (FCM) for Android to send notifications to the app. These credentials are issued by the push vendors themselves.

Both, iOS and Android Push Credentials, are centrally managed in the console using Mobile Push Credentials. For more information, see the detailed guide on generating credentials for iOS and Android.

About Certificate ID

Unique Certificate ID is generated for each Push credential uploaded on the Plivo console. To enable incoming calls for a Plivo Endpoint, register the endpoint using an endpoint username, password, device token, and the Certificate ID. Register Plivo endpoint using the method for iOS and Android. Presently, users can upload up to 10 certificates per account on the console.

About Default FCM and APNS certificates

The default certificate will be used to send Push notifications for the Plivo Endpoints that are not registered using any Certificate ID. (For more information, see Registering a Method for iOS and Android).

Note: It is recommended to always use Certificate ID while registering a Plivo Endpoint. (Register Plivo endpoint using the method for iOS and Android.

Each iOS and Android platform has one default certificate per account, which is denoted by the “Default APNS” and “Default FCM” tags. You can change the default certificate anytime using Certificate Edit option.

Add a Push Credential

Both iOS and Android Push Credentials are centrally managed in the console using Mobile Push Credentials. Android uses the FCM certificate type and iOS uses APNS certificate type. You can upload up to 10 certificates per account on the console.

Adding iOS push credential

Adding Android push credential

Updating a Push Credential

You can update a push credential using the Edit option. The Certificate ID will not change for any consecutive updates to a certificate.

You need not re-upload the certificate to reassign the default certificate

Note: You can change the environment from sandbox to production, but not from production to sandbox. To change your environment to sandbox from production, upload a new certificate with sandbox as the environment.

Delete a Push Credential

It is not recommended to delete a Push Credential unless the application that it was created for is no longer required. If you delete a Push credential, it cannot be reverted. When a Push credential is deleted, all incoming calls to the associated Endpoint will fail. You can delete a Push credential using the Delete option present in Console, under Mobile Push Credentials.

Deleting a default certificate

If more than one certificate is present of a particular platform (iOS/Android), you have to assign another certificate as the default certificate before deleting the present default certificate of that platform. Whereas, if a single certificate is present for a particular platform, the user can delete the certificate without any assignment.

Troubleshooting

How do I recover deleted certificate?

Deleted certificates cannot be recovered, but the same Certificate ID can. Certificate ID is generated using Account Auth ID and Certificate Name on the console. If a certificate is uploaded with the same Certificate Name, the new certificate will have the same Certificate ID. Also, the endpoint associated with that certificate ID will start using the same credentials for push notifications.

I am unable to add more than 10 certificates.

We have a limit of 10 certificates per account irrespective of the platform (iOS and Android). If your business use case requires more than 10 certificates, reach out to our support team.

The certificate is uploaded, but I am not receiving any incoming call alerts.

Make sure the endpoint is registered using the uploaded certificate’s ID. For more information, see the troubleshooting guide.

Default certificate usage:

With v2.1.4 for iOS and v2.0.6 for Android, we have introduced new Login methods to explicitly specify Certificate ID used for incoming call push notifications. But, if you are still using Login method without Certificate ID, then default certificate uploaded on the console will be used to send push notifications to devices.