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 |
|---|---|---|
| All | Personalisation issue (wrong syntax, missing attribute or missing fallback value, twig not enabled for project). |
| App push | The app has been uninstalled or it cannot longer be reached from the gateway |
| Android push | The sender ID uploaded to the XtremePush platform doesn't match the sender ID used to generate the push token. |
iOS push | Expired iOS certificate. Replace it following instructions here. | |
| iOS push | Expired iOS certificate. Replace it following instructions here. |
| iOS push | Token mismatch (possibly using sandbox token for production app or viceversa). |
| SMS | From name is not correct. Must follow format outlined here. |
| Web push | The subscription for the device is no longer active or the service worker on that particular device has been removed. |
| iOS push | The app push certificate and bundle ID are mismatched. |
| Android push | The app has been uninstalled or the token hasn't been refreshed in 270 days. Marks the device as unaddressable. |
| Android push | Firebase applies a sending limit that has been exceeded. Contact Firebase to get this limit increased. |
| Android push | FCM v1 API is disabled in your Firebase project. Review your configuration. |
Updated 1 day ago