Status code |
Error string |
Description |
---|---|---|
|
|
The collapse identifier exceeds the maximum allowed size |
|
|
The specified device token was bad. Verify that the request contains a valid token and that the token matches the environment. |
|
|
The |
|
|
The |
|
|
The |
|
|
The |
|
|
The device token does not match the specified topic. |
|
|
One or more headers were repeated. |
|
|
Idle time out. |
|
|
The device token is not specified in the request |
|
|
The |
|
|
The message payload was empty. |
|
|
Pushing to this topic is not allowed. |
|
|
The certificate was bad. |
|
|
The client certificate was for the wrong environment. |
|
|
The provider token is stale and a new token should be generated. |
|
|
The specified action is not allowed. |
|
|
The provider token is not valid or the token signature could not be verified. |
|
|
No provider certificate was used to connect to APNs and Authorization header was missing or no provider token was specified. |
|
|
The request contained a bad |
|
|
The specified |
|
|
The device token is inactive for the specified topic. Expected HTTP/2 status code is Status codes for an APNs response table |
|
|
The message payload was too large. See Creating the Remote Notification Payload for details on maximum payload size. |
|
|
The provider token is being updated too often. |
|
|
Too many requests were made consecutively to the same device token. |
|
|
An internal server error occurred. |
|
|
The service is unavailable. |
|
|
The server is shutting down. |
Status code |
Description |
---|---|
200 |
Success |
400 |
Bad request |
403 |
There was an error with the certificate or with the provider authentication token |
405 |
The request used a bad |
410 |
The device token is no longer active for the topic. |
413 |
The notification payload was too large. |
429 |
The server received too many requests for the same device token. |
500 |
Internal server error |
503 |
The server is shutting down and unavailable. |
For more information please refer to the following Documentation:
Comments
0 comments
Please sign in to leave a comment.