Configuration Instruction for PushKit

Content

1. Create VoIP certificate
2. Upload to CommsEase server
3. Realization
4. Troubleshoot the problem of being unable to receive push from PushKit

PushKit framework is used for sending specific notifications to the developer's apps, for example, VoIP (Voice over IP), watchOS, and other component updates. Among them, VoIP push can help improve experience of VoIP app. Next, we introduce PushKit configuration required for such app.

Create VoIP certificate

To receive a push notification, we shall first create an Identifier.

A bundle id is designated to the app. ** com.emily.voiptest ** is taken as an example here. Do not worry about options under App Service. You can fill in later.

The identifier has been set now. Next, the certificate required for push notification shall be configured.

Next, an App ID shall be selected. The newly created ID is selected here. Next, we introduce the step of creating CSR certificate with keychain:

Download certificate and click to automatically import keychain. Find your certificate and click a small arrow around the certificate, get a certificate and corresponding key.

Select p12 format and name it. Be attention to file format as shown below:

2. Upload to CommsEase server

• Visit CommsEase website and select the corresponding app.
• Upload the exported p12 file and make a distinction by the certificate that is filled in when uploading.
• Please select the same environment ("development environment" or "production environment") where the certificate is generated.

3. Realization

• Please ensure that "bundle identifier" of the create project must be the same with a certificate, so that push can be sent.
• Open "Voice over IP" under option "capabilities->background Modes" of "Target"
• Introduce PushKit service

4. Troubleshoot the problem of being unable to receive push from PushKit

• You shall confirm the configuration of the certificate firstly. See above Article 1 & 2 for configuration in detail.
• If the certificate is configured correctly, you shall download the local pusher tool to test that message can be received. README file in the tool contains installation

The API is shown in the above Figure.

PushKit token is obtained using functional log in AppDelegate file.

Push is made after configuration. If push is successful, you can see at the bottom left corner and see push with red corner mark "555" on app icon in your phone.

Otherwise, you shall check as below:

1. Check that push certificate is correctly configured in the background;
2. Check that cername filled at initialization is consistent with the one configured at management console;
3. Check that private key is contained in packaging certificate;
4. Check that provisioning profile contains new push certificate;
5. Check cername in SDK Log is consistent with the one in Step 3;
6. Check that deviceToken can be obtained using code debugging.

If you still have any problem after trying the above steps, please contact related technical assistance staff to provide a solution.