Using Push Notifications
Starting with SDK v1.17 the SDK requires a server upgrade in case you are migrating from a previous version (you need to contact IMS for that) and the server requires push notification capabilities.
Steps to follow for using the push notifications for phone only trip detection
App needs to create the push notification certificate with Apple app store connect.
The guide for creating the push notification certificate+profile and how to export the certificate as a .p12 file can be found here.
After successful submission of certificate, system will create a unique device token for the respective device
Note: Helpful system apis to verify if the registration of remote push notification is successful or not.
These two functions should be in AppDelegate.swift
file in order to verify the registration of remote push notifications
The device token needs to be passed to SDK using the PushNotificationService to set the token on DriveSync and the device will be registered to receive push notification from DriveSync.
Upon successful registration of device token, the token can be passed to the SDK PushNotificationService
to set the token on DriveSync.
Please refer to this page for using the service.
Once the device token is set to DriveSync, the server will be sending silent push notifications to wake up the app in the background and to improve trip detection.
No steps are required on the host app upon receiving silent push notifications except making sure the required permissions are there to facilitate the feature.
Required permissions
Allow push notification permission
Will be asked during onboarding
Background app refresh permission
Needs to be checked in
info.plist
of the host app
Last updated