| Status code | Error string | Description |
|---|---|---|
| 400 | BadCollapseId | The collapse identifier exceeds the maximum allowed size |
| 400 | BadDeviceToken | The specified device token was bad. Verify that the request contains a valid token and that the token matches the environment. |
| 400 | BadExpirationDate | The apns-expiration value is bad. |
| 400 | BadMessageId | The apns-id value is bad. |
| 400 | BadPriority | The apns-priority value is bad. |
| 400 | BadTopic | The apns-topic was invalid. |
| 400 | DeviceTokenNotForTopic | The device token does not match the specified topic. |
| 400 | DuplicateHeaders | One or more headers were repeated. |
| 400 | IdleTimeout | Idle time out. |
| 400 | MissingDeviceToken | The device token is not specified in the request :path. Verify that the :path header contains the device token. |
| 400 | MissingTopic | The apns-topic header of the request was not specified and was required. The apns-topic header is mandatory when the client is connected using a certificate that supports multiple topics. |
| 400 | PayloadEmpty | The message payload was empty. |
| 400 | TopicDisallowed | Pushing to this topic is not allowed. |
| 403 | BadCertificate | The certificate was bad. |
| 403 | BadCertificateEnvironment | The client certificate was for the wrong environment. |
| 403 | ExpiredProviderToken | The provider token is stale and a new token should be generated. |
| 403 | Forbidden | The specified action is not allowed. |
| 403 | InvalidProviderToken | The provider token is not valid or the token signature could not be verified. |
| 403 | MissingProviderToken | No provider certificate was used to connect to APNs and Authorization header was missing or no provider token was specified. |
| 404 | BadPath | The request contained a bad :path value. |
| 405 | MethodNotAllowed | The specified :method was not POST. |
| 410 | Unregistered | The device token is inactive for the specified topic.Expected HTTP/2 status code is 410; see Table 8-4. |
| 413 | PayloadTooLarge | The message payload was too large. See Creating the Remote Notification Payload for details on maximum payload size. |
| 429 | TooManyProviderTokenUpdates | The provider token is being updated too often. |
| 429 | TooManyRequests | Too many requests were made consecutively to the same device token. |
| 500 | InternalServerError | An internal server error occurred. |
| 503 | ServiceUnavailable | The service is unavailable. |
| 503 | Shutdown | The server is shutting down. |
APNs 错误码
©著作权归作者所有,转载或内容合作请联系作者
- 文/潘晓璐 我一进店门，熙熙楼的掌柜王于贵愁眉苦脸地迎上来，“玉大人，你说我怎么就摊上这事。” “怎么了？”我有些...
- 文/花漫 我一把揭开白布。 她就那样静静地躺着，像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上，一...
- 文/苍兰香墨 我猛地睁开眼，长吁一口气：“原来是场噩梦啊……” “哼！你这毒妇竟也来了？” 一声冷哼从身侧响起，我...
推荐阅读更多精彩内容
- Status codeError stringDescription400BadCollapseIdThe col...
- 版本记录 前言 我们做APP很多时候都需要推送功能，以直播为例，如果你关注的主播开播了，那么就需要向关注这个主播的...
- 本文的大部分内容是对苹果关于APNs官方文档的翻译以及整理。 一、设备token和消息的生命周期 关于设备toke...
