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:
If your application has generated errors you can find them in a list as the one below:
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:
Below you'll find the list of possible errors for each platform:
Apple Push Notifications Errors
Common errors found when sending messages via APNS.
Error | Description |
---|---|
The collapse identifier exceeds the maximum allowed size | The system attempt to send a message that contained a collapse identifier bigger than what is allowed. |
The specified device token was bad | The system tried to deliver a message to a device token that was malformed or was not registered for this environment. The device was deactivated. Possible solution: Confirm the built application targets a Notificare DEV or PROD app for Debug or Release builds, respectively. For more information check the troubleshooting guide. |
The apns-expiration value is bad | The system attempt to send a message that contained an invalid apns-expiration . |
The apns-id value is bad | The system attempt to send a message that contained an invalid apns-expiration . |
The apns-priority value is bad | The system attempt to send a message that contained an invalid apns-priority . |
The apns-topic was invalid | The system attempt to send a message that contained an invalid apns-topic . |
The device token does not match the specified topic | The system tried to deliver a message to a device token that is not registered for this topic. The device was deactivated. Possible solution: Confirm the bundle identifier of the app matches the configured value in the Notificare APNS service. |
One or more headers were repeated | The system attempt to send a message that contained duplicated headers. |
Idle time out | The system was disconnected due to inactivity. |
The device token is not specified in the request | The 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 required | The system attempt to send a message that did not contain an apns-topic . |
The message payload was empty | The system attempt to send a message that did not contain a payload. |
Pushing to this topic is not allowed | The system attempt to send a message to a topic that does not allow messages. |
The certificate was bad | The system attempt to send a message using an invalid certificate. |
The client certificate was for the wrong environment | The 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 generated | The system attempt to send a message using a stale provider token and a new one was generated. |
The specified action is not allowed | The system attempt to perform an invalid operation. |
The provider token is not valid or the token signature could not be verified | The system attempt to send a message using an invalid provider token. |
No provider certificate was used or no provider token was specified | The system attempt to send a message without a certificate or provider token. |
The request contained a bad :path value | The system attempt to send a message that contained a bad :path . |
The specified :method was not POST | The system attempt to send a message where :method was not POST. |
The device token is inactive for the specified topic | The 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 large | The system tried to deliver a message with a payload bigger than what is allowed. |
The provider token is being updated too often | The system tried to update the provider token too often. |
Too many requests were made consecutively to the same device token | The system tried to deliver too many messages for the same device token. |
An internal server error occurred | The system received a internal server error when reaching APNS and could not process the message. |
The service is unavailable | The system could not reach APNS and could not process the message. |
The server is shutting down | The system received a shutdown error from APNS and could not process the message. |
Unknown error | The system got an unknown error and could not process the message. |
GCM/FCM Errors
Common errors found when sending messages via GCM/FCM.
Error | Description |
---|---|
GCM/FCM unavailable | The system failed to connect to GCM/FCM because the service is unavailable |
Connection error | The system failed to connect to GCM/FCM due to a network error |
Authentication error | The system failed to connect to GCM/FCM due to a wrong Server Key |
Device is unavailable | The system tried to deliver a message but the device was not available at that time |
Device is not registered | The system tried to deliver a message to a device token that was not registered for this app. The device was deactivated. |
Unknown error | The 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.
Error | Description |
---|---|
Failed after retries | The system tried to deliver a message several time and failed to deliver it. |
Device is not registered | The system tried to send a notification to a token that was not registered for this website. The device was deactivated. |
Invalid payload or authentication mismatch | System could not connect to VAPID (probably wrong VAPID) |
Authentication error | System could not connect to VAPID or GCM (most likely wrong VAPID or device auth key) |
Unknown error | The system got an unknown error and could not process the message |
Email Errors
Common errors found when sending email messages via our SMTP servers.
Error | Description |
---|---|
Insufficient email credit | The message could not be sent because there was not enough email credit on the account balance |
Message rejected | The message could not be sent because of missing or invalid recipient |
Service unavailable | The message could not be sent due to a temporary failure of the server |
Error sending message | The message could not be sent for reasons other than the ones described here |
Recipient was suppressed | The 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 exist | The intended recipient's email provider sent a bounce message indicating that the email address doesn't exist. The recipient was deactivated. |
Recipient not accepted | The 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 large | The 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 rejected | The 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 rejected | The 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 unknown | The 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: Abuse | Indicates unsolicited email or some other kind of email abuse. The recipient was deactivated. |
Received complaint: Auth-Failure | Email authentication failure report |
Received complaint: Fraud | Indicates some kind of fraud or phishing activity. The recipient was deactivated. |
Received complaint: Other | Indicates any other feedback that does not fit into other registered types. The recipient was deactivated. |
Received complaint: Virus | Reports that a virus is found in the originating message |
Sender domain not verified | The 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.
Error | Description |
---|---|
Insufficient SMS credit | The message could not be sent because there was not enough SMS credit on the account balance. |
Queue overflow | You tried to send too many messages too quickly, and your message queue overflowed. Try sending your message again after waiting for some time. |
Unknown destination | The destination number you are trying to reach is unknown and may no longer exist. |
Unreachable carrier | The destination number is unable to receive this message. Potential reasons could include trying to reach a landline or an unreachable carrier. |
Error sending message | The error does not fit into any of the above categories. |
Unreachable destination | The destination handset you are trying to reach is switched off or otherwise unavailable. |
Message blocked | The destination number you are trying to reach is blocked from receiving this message (e.g., due to blacklisting) |
Carrier violation | Your message was flagged as objectionable by the carrier. To protect their subscribers, many carriers have implemented content or spam filtering. |
Error delivering message | The error does not fit into any of the above categories. |