Skip to content

Remote Notifications

Andy Johns edited this page Feb 19, 2016 · 1 revision

###Remote Notification Registration

If properly configured with a valid remote notification supporting provisioning profile, the SDK will create and maintain a data document that contains the remote notification token and other pertinent data.

The document contains:

  • DeviceToken - Base64 encoded remote notification device token
  • DeviceModel - The model of the device. Possible examples of model strings are iPhone, iPad, and iPod touch
  • OSVersion - The current version of the operating system. An example of the system version is 9.3
  • DeviceVendorID - GUID string of the device's unique vendor identifier
  • AppBundleId - The app's bundle id
  • AppBuildVersion - The app's short version string
  • AppVersion - The app's bundle version string
  • Locale - The device's current locale string
  • TimeZone - The device's current Timezone abbreviation. An examples are PDT, EST, GMT+12
  • UserData - The user information dictionary obtained during authentication.
  • Additional - An optional dictionary of data provided by the Container application
  • type : The string RemoteNotificationRegistration
  • _id : doc_RNR_{DeviceVendorID}

The Additional data dictionary is configured using the remoteNotificationRegistrationAdditionalInfo property of PredixMobilityConfiguration.

Once created, this document will be kept up to date. For example, if the user information changes, the token changes, or the device is upgraded to a new OS version, the document will be updated accordingly.


Receiving Remote Notifications

The APNS meta-data dictionary will be examined for a "script" element. If this element is present, the value of this element will be used as a JavaScript name passed to the webapp. The APNS meta-data dictionary will be passed as a parameter to this script.