Updated Apple Push Notification Service for iOS Notifications

We’re switching from legacy binary push to HTTP/2 push in Summer ‘18. You can now use provider authentication tokens in addition to provider certificates to enable push messaging. Unlike provider certificates, provider authentication tokens don’t expire saving admins and app users time.

Where: This feature is available for Salesforce for iOS, in all editions except Database.com.

Why: Apple plans to eventually depreciate support for legacy binary push, so we’re moving to HTTP/2 push in anticipation of that change.

How: To use provider authentication tokens, update Mobile Settings in your connected app.

Type App Manager into the Quick Find box in Setup then navigate to New Connected App. In the Mobile App Settings section, perform these steps.
  1. For App Platform, select iOS.
  2. Select Push Messaging Enabled. The dialog box expands to show more settings.
  3. For Platform, select Apple.
  4. Upload Signing Key from your Apple developer account.
  5. Enter the Key Identifier from your Apple developer account.
  6. Enter the Team Identifier from your Apple developer account.
Step by step instructions with six callouts for setting up token authentication in setup for iOS.


You can use authentication tokens, push certificates, or both. If a token is provided, Salesforce always uses the token. We also use Application Bundle ID when it is provided. We recommend using Application Bundle ID to avoid problems with your push notification settings.