Common notifications log errors
Review the most common reasons messages fail and how to fix them
In some situations, individual sends or a whole batch of messages can fail. See below for a list of the most common errors:
| Error message | Channel | Meaning |
|---|---|---|
Not personalised | All | Personalisation issue (wrong syntax, missing attribute or missing fallback value, twig not enabled for project). |
Device_unregistered | App push | The app has been uninstalled or it cannot longer be reached from the gateway |
Sender_ID_mismatch | Android push | The sender ID uploaded to the XtremePush platform doesn't match the sender ID used to generate the push token. |
Post "https://api.push.apple.com...` | iOS push | Expired iOS certificate. Replace it following instructions here. |
Unable to connect to 'ssl://gateway.push.apple.com... | iOS push | Expired iOS certificate. Replace it following instructions here. |
BadDeviceToken | iOS push | Token mismatch (possibly using sandbox token for production app or viceversa). |
Invalid from param | SMS | From name is not correct. Must follow format outlined here. |
Gone | Web push | The subscription for the device is no longer active or the service worker on that particular device has been removed. |
DeviceTokenNotForTopic | iOS push | The app push certificate and bundle ID are mismatched. Verify that the bundle ID saved in Xtremepush (application settings) matches exactly the bundle ID in the application source code. |
404: Requested entity was not found | Android push | The app has been uninstalled or the token hasn't been refreshed in 270 days. Marks the device as unaddressable. |
429: Quota exceeded for quota metric... | Android push | Firebase applies a sending limit that has been exceeded. Contact Firebase to get this limit increased. |
403: Firebase Cloud Messaging API has not been used in project XXX before | Android push | FCM v1 API is disabled in your Firebase project. Review your configuration. |
Updated 6 months ago