| 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 push推送錯誤定位/錯誤碼
最后編輯于 :
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成,瀏覽時請結(jié)合常識與多方信息審慎甄別。
平臺聲明:文章內(nèi)容(如有圖片或視頻亦包括在內(nèi))由作者上傳并發(fā)布,文章內(nèi)容僅代表作者本人觀點,簡書系信息發(fā)布平臺,僅提供信息存儲服務(wù)。
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成,瀏覽時請結(jié)合常識與多方信息審慎甄別。
平臺聲明:文章內(nèi)容(如有圖片或視頻亦包括在內(nèi))由作者上傳并發(fā)布,文章內(nèi)容僅代表作者本人觀點,簡書系信息發(fā)布平臺,僅提供信息存儲服務(wù)。
相關(guān)閱讀更多精彩內(nèi)容
- 版本記錄 前言 我們做APP很多時候都需要推送功能,以直播為例,如果你關(guān)注的主播開播了,那么就需要向關(guān)注這個主播的...