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
Sending Mobile Notifications
Using the Connect REST API Push Notification Resource (Optional)
Reference
PushNotificationPayload Class
Apex Limits Functions for Push Notifications
Push Notification Limits
Error Messages for Push Notifications
Debug Log Events
Notifications Resources
Notification Builder Platform Push Payloads
Invocable Actions Custom
PDF

Error Messages for Push Notifications

If you get an error message while sending a push notification from the Send Test Notification page, check the following table for suggestions on how to fix the error.
Message Suggested Resolution
Daily push rate limit has been exceeded for this connected application Because the daily limit is nonnegotiable, no resolution is available.
Certificate is not accepted by Apple Push Notification service Replace the certificate with a valid type.
Certificate is revoked Supply valid certificate.
Certificate expired Renew certificate.
Certificate not valid yet Retry later.
Invalid certificate or password Replace the certificate with a valid type.
Invalid recipient or payload Check your input for errors.
Payload exceeds maximum size Reduce size of payload.
Unable to load push notifications settings Confirm that settings are present on connected app.
Recipient field contains invalid device token Provide valid device token.
Invalid device token length Token was entered incorrectly or is corrupt. Re-enter token.
Error while sending notification. Confirm certificate is for the correct Apple environment. Confirm that correct certificate is being used (for example, sandbox versus production).
Apple Push Notification service is unavailable. Retry later.
Unable to connect to Apple Push Notification service Retry later.
Unable to connect to Salesforce proxy. Contact Salesforce support if issue persists. Retry later.
Request blocked by Salesforce proxy. Contact Salesforce support if issue persists. Retry later.
Apple Push Notification service returned unknown error Contact Apple or retry later.
Badge must be a number Re-enter the badge value as an integer.
Payload must be in a valid JSON format Format payload correctly.
You must enter a value for at least one of the following fields: Alert, Badge, Sound, or Custom Payload Enter a valid value for one of the fields.
Recipient is required Provide device token.
Firebase Cloud Messaging authentication error Consult the FCM documentation at developer.android.com. Possible causes:

  • Authorization header is missing or contains invalid syntax.

  • Invalid project number was sent as key.

  • Key is valid, but FCM service is disabled.

  • Request originated from a server that is not white-listed in the server key IP addresses.
Internal error in the Firebase Cloud Messaging server, or the server is temporarily unavailable Retry later.
Registration ID in the Recipient field is formatted incorrectly Verify that mobile app is providing valid registration ID, or manually enter valid registration ID.
Payload exceeds maximum size Reduce size of payload.
Recipient field contains registration ID that is not valid for the connected application’s API server key Provide correct server key for the app.
Recipient is required Select recipient or provide registration ID.
Recipient field contains invalid registration ID Update recipient’s device registration ID.
FCM server returned an unexpected error. Please contact the SFDC support team. Contact Salesforce.
An unexpected error occurred. Please contact the SFDC support team. Contact Salesforce.