Guides

Errors

Under this area you can quickly find all the errors your application generates. You will mostly find here errors related with APNS or GCM/FCM authentication, messages that coupld not be delivered and devices that no longer exist.

In any of your apps you'll find a menu item called Errors as follows:

menu

If your application has generated errors you can find them in a list as the one below:

list

Because these errors are merely informative, you can at any moment clear this list by using the Options menu in the top right corner and clicking in Clear All:

options clear all

Below you'll find the list of possible errors for each platform:

Apple Push Notifications Errors

Common errors found when sending messages via APNS.

ErrorDescription
The collapse identifier exceeds the maximum allowed sizeThe system attempt to send a message that contained a collapse identifier bigger than what is allowed.
The specified device token was badThe system tried to deliver a message to a device token that was malformed or was not registered for this environment. The device was deactivated.
The apns-expiration value is badThe system attempt to send a message that contained an invalid apns-expiration.
The apns-id value is badThe system attempt to send a message that contained an invalid apns-expiration.
The apns-priority value is badThe system attempt to send a message that contained an invalid apns-priority.
The apns-topic was invalidThe system attempt to send a message that contained an invalid apns-topic.
The device token does not match the specified topicThe system tried to deliver a message to a device token that is not registered for this topic. The device was deactivated.
One or more headers were repeatedThe system attempt to send a message that contained duplicated headers.
Idle time outThe system was disconnected due to inactivity.
The device token is not specified in the requestThe system attempt to send a message that did not contain a device token.
The apns-topic header of the request was not specified and was requiredThe system attempt to send a message that did not contain an apns-topic.
The message payload was emptyThe system attempt to send a message that did not contain a payload.
Pushing to this topic is not allowedThe system attempt to send a message to a topic that does not allow messages.
The certificate was badThe system attempt to send a message using an invalid certificate.
The client certificate was for the wrong environmentThe system attempt to send a message using a certificate issued for a different environment.
The provider token is stale and a new token should be generatedThe system attempt to send a message using a stale provider token and a new one was generated.
The specified action is not allowedThe system attempt to perform an invalid operation.
The provider token is not valid or the token signature could not be verifiedThe system attempt to send a message using an invalid provider token.
No provider certificate was used or no provider token was specifiedThe system attempt to send a message without a certificate or provider token.
The request contained a bad :path valueThe system attempt to send a message that contained a bad :path.
The specified :method was not POSTThe system attempt to send a message where :method was not POST.
The device token is inactive for the specified topicThe system tried to deliver a message to a device token that is no longer registered for this topic. The device was deactivated.
The message payload was too largeThe system tried to deliver a message with a payload bigger than what is allowed.
The provider token is being updated too oftenThe system tried to update the provider token too often.
Too many requests were made consecutively to the same device tokenThe system tried to deliver too many messages for the same device token.
An internal server error occurredThe system received a internal server error when reaching APNS and could not process the message.
The service is unavailableThe system could not reach APNS and could not process the message.
The server is shutting downThe system received a shutdown error from APNS and could not process the message.
Unknown errorThe system got an unknown error and could not process the message.

GCM/FCM Errors

Common errors found when sending messages via GCM/FCM.

ErrorDescription
GCM/FCM unavailableThe system failed to connect to GCM/FCM because the service is unavailable
Connection errorThe system failed to connect to GCM/FCM due to a network error
Authentication errorThe system failed to connect to GCM/FCM due to a wrong Server Key
Device is unavailableThe system tried to deliver a message but the device was not available at that time
Device is not registeredThe system tried to deliver a message to a device token that was not registered for this app. The device was deactivated.
Unknown errorThe system got an unknown error and could not process the message

Web Push Notifications Errors

Common errors found when sending web push notifications via GCM, Safari Web Push and VAPID.

ErrorDescription
Failed after retriesThe system tried to deliver a message several time and failed to deliver it.
Device is not registeredThe system tried to send a notification to a token that was not registered for this website. The device was deactivated.
Invalid payload or authentication mismatchSystem could not connect to VAPID (probably wrong VAPID)
Authentication errorSystem could not connect to VAPID or GCM (most likely wrong VAPID or device auth key)
Unknown errorThe system got an unknown error and could not process the message

Email Errors

Common errors found when sending email messages via our SMTP servers.

ErrorDescription
Insufficient email creditThe message could not be sent because there was not enough email credit on the account balance
Message rejectedThe message could not be sent because of missing or invalid recipient
Service unavailableThe message could not be sent due to a temporary failure of the server
Error sending messageThe message could not be sent for reasons other than the ones described here
Recipient was suppressedThe recipient's email address is on the suppression list because it has a recent history of producing hard bounces. The recipient was deactivated.
Recipient does not existThe intended recipient's email provider sent a bounce message indicating that the email address doesn't exist. The recipient was deactivated.
Recipient not acceptedThe recipient's email provider sent a hard bounce message, but didn't specify the reason for the hard bounce. The recipient was deactivated.
Message too largeThe recipient's email provider sent a bounce message because message you sent was too large. You might be able to send a message to the same recipient if you reduce the size of the message.
Content rejectedThe recipient's email provider sent a bounce message because the message contained an unacceptable attachment. For example, some email providers may reject messages with attachments of a certain file type, or messages with very large attachments. You might be able to send a message to the same recipient if you remove or change the content of the attachment.
Attachment rejectedThe recipient's email provider sent a bounce message because the message you sent contains content that the provider doesn't allow. You might be able to send a message to the same recipient if you change the content of the message.
Reason unknownThe recipient's email provider sent a bounce message. The bounce message didn't contain enough information to determine the reason for the bounce.
Received complaint: AbuseIndicates unsolicited email or some other kind of email abuse. The recipient was deactivated.
Received complaint: Auth-FailureEmail authentication failure report
Received complaint: FraudIndicates some kind of fraud or phishing activity. The recipient was deactivated.
Received complaint: OtherIndicates any other feedback that does not fit into other registered types. The recipient was deactivated.
Received complaint: VirusReports that a virus is found in the originating message
Sender domain not verifiedThe message could not be sent because the MX record required to use the specified sender domain could not be verified

SMS Errors

Common errors found when sending SMS messages via our system.

ErrorDescription
Insufficient SMS creditThe message could not be sent because there was not enough SMS credit on the account balance.
Queue overflowYou tried to send too many messages too quickly, and your message queue overflowed. Try sending your message again after waiting for some time.
Unknown destinationThe destination number you are trying to reach is unknown and may no longer exist.
Unreachable carrierThe destination number is unable to receive this message. Potential reasons could include trying to reach a landline or an unreachable carrier.
Error sending messageThe error does not fit into any of the above categories.
Unreachable destinationThe destination handset you are trying to reach is switched off or otherwise unavailable.
Message blockedThe destination number you are trying to reach is blocked from receiving this message (e.g., due to blacklisting)
Carrier violationYour message was flagged as objectionable by the carrier. To protect their subscribers, many carriers have implemented content or spam filtering.
Error delivering messageThe error does not fit into any of the above categories.