Managing Push Credentials

    You must have a valid push credential to receive incoming call alerts using iOS and Android apps. The Plivo Mobile SDKs integrate Apple Push Notification service (APNs) for iOS and Firebase Cloud Messaging (FCM) for Android to send notifications to apps. The push vendors themselves issue the push credentials.

    You can manage iOS and Android push credentials using Voice > Push Credentials on the Plivo console. For setup instructions, see Setting Up Push Notification for iOS and Android SDKs.

    About Certificate ID

    Plivo generates a unique Certificate ID for each push credential uploaded on the console. To enable incoming calls for a Plivo endpoint, register the endpoint using an endpoint username, password, device token, and Certificate ID for either iOS or  Android. You can upload up to 10 certificates per account on the console.

    About Default FCM and APNs certificates

    Plivo uses a default certificate to send push notifications for Plivo endpoints that are not registered using any Certificate ID. (For more information, see Registering an Endpoint for iOS and Android.)

    Note: We recommend you always use a Certificate ID when 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 Default APNS and Default FCM tags. You can change the default certificate at any time from the console’s Voice > Push Credentials screen.

    Default FCM

    Adding a push credential

    You can manage both iOS and Android push credentials in the console at Voice > Push Credentials. iOS uses the APNS certificate type and Android uses the FCM certificate type. You can upload up to 10 certificates per account on the console.

    Adding an iOS push credential

    Adding iOS Push Credential

    Adding an Android push credential

    Adding Android Push Credential

    Updating a push credential

    You can update a push credential by visiting Voice > Push Credentials and clicking on a credential name. The Certificate ID will not change for any consecutive updates to a certificate.

    You need not reupload 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.

    Updating a Push Credential

    Deleting a push credential

    We do not recommend deleting a push credential unless the application that it was created for is no longer required. If you delete a push credential, your change 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 in the console under Voice > Push Credentials.

    Deleting a default certificate

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

    Deleting a default certificate

    Troubleshooting

    How can I recover a deleted certificate?

    You can’t recover a deleted certificate, but you can generate the same Certificate ID. Plivo generates a Certificate ID using the Account Auth ID and Certificate Name on the console. If you upload a certificate 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.

    Why can’t I 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’m not receiving any incoming call alerts.

    Make sure the endpoint is registered using the uploaded Certificate ID. For more information, see the Moible SDK Troubleshooting Guide.

    Default certificate usage:

    With iOS SDK v2.1.4 and Android SDK v2.0.6, we introduced new Login methods to explicitly specify the Certificate ID used for incoming call push notifications. If you’re still using the Login method without a Certificate ID, then Plivo will use the default certificate uploaded on the console to send push notifications to devices.