Salesforce Mobile Notifications Implementation Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Mobile Notifications Overview
Steps for Implementing Mobile Notifications
Step 1. Developer Registration with Mobile OS Vendors
Step 2. Creating a Connected App
Step 3. Configure Your Mobile SDK App
Enable Push Notifications in a Salesforce Mobile SDK Android App
Enable Push Notifications in a Salesforce Mobile SDK iOS App
Enable Push Notifications in a Salesforce Mobile SDK Hybrid App
Handle Notification Encryption in Salesforce Mobile SDK Apps
Build Your Own In-App Notification Feature
Step 4. Packaging Components for Customer Organizations
Sending Mobile Notifications
Using the Connect REST API Push Notification Resource (Optional)
Reference
PDF

Handle Notification Encryption in Salesforce Mobile SDK Apps

Mobile notifications travel from Salesforce, through third-party messaging services to mobile carriers, then on to mobile devices. Such an indirect path only increases the opportunities for malicious attacks. To guard against snooping or hacking, Salesforce encrypts Notification Builder notifications. Your app is responsible for decrypting these notifications.

Setting up encryption for notifications requires no configuration on the server. For client-side decryption, Salesforce Mobile SDK does most of the work for you. Mobile SDK negotiates the encryption policy with the Salesforce server and internally handles the exchange of public and private keys.

Your tasks for notification decryption on client apps depends on the mobile operating system.
iOS
Apps that are registered for Salesforce notifications must extend the UNNotificationServiceExtension class. A specialized Mobile SDK template app provides a boilerplate extension that you can bring into your iOS app, provided you’re using Mobile SDK 8.2 or later. Earlier versions of Mobile SDK do not fully support notification encryption.
Android
Mobile SDK for Android handles decryption internally and requires no client-side code changes.

Implementing a Decryption Extension (Swift)

In Mobile SDK 8.2 and later, the forceios iOSNativeSwiftTemplate app requests notification authorization through the iOS UNUserNotificationCenter object. A specialized version of iOSNativeSwiftTemplate, iOSNativeSwiftEncryptedNotificationTemplate, extends the UNNotificationServiceExtension iOS class to handle notification decryption. This extension class, NotificationService, provides boilerplate decryption code that Mobile SDK apps can use without changes. To support encrypted notifications, you must be using Mobile SDK 8.2 or later, and your app must include this extension.

To create a Swift project that supports Notification Builder encrypted notifications, you can use the iOSNativeSwiftEncryptedNotificationTemplate template with forceios. Even if you’re updating an existing Mobile SDK project, it’s easiest to start fresh with a new forceios template project. If you’d rather update a Swift project manually, skip to “Example: Add Push Registration Manually (Swift)”.
  1. Install the latest forceios version from node.js:
    [sudo] npm install -g forceios
  2. Call the forceios createWithTemplate command:
    forceios createWithTemplate
  3. At the first prompt, enter iOSNativeSwiftEncryptedNotificationTemplate:
    forceios createWithTemplate
Enter URI of repo containing template application or a Mobile SDK template name: 
    iOSNativeSwiftEncryptedNotificationTemplate
  4. In the remaining prompts, enter your company and project information. If your information is accepted, forceios creates a project that is ready for encrypted notifications.
  5. If you’re updating an older Mobile SDK project, copy your app-specific resources from your old project into the new project.

See Also