前段时间，仔细研究了APNS的文档，把一些关键的地方记录了下来，弄懂这些对于理解APNS的规则，至关重要。

1. If APNs attempts to deliver a notification but the device is offline, the notification is stored for a limited period of time, and delivered to the device when it becomes available.

假如用户手机不在线，可能没有信号或者关机吧，APNs会存储转发，等用户在线时再发送

2.Only one recent notification for a particular application is stored. If multiple notifications are sent while the device is offline, each new notification causes the prior notification to be discarded. This behavior of keeping only the newest notification is referred to as coalescing notifications.

如果用户不在线，通知会合并，只会保留最新的一条。假如你给用户发了两条通知，但用户反馈说，只收到了一条，那么很可能是用户当时不在线，APNs的合并策略生效，只保留了最近一条

3.If the device remains offline for a long time, any notifications that were being stored for it are discarded

4.The maximum size allowed for a notification payload is 256 bytes; Apple Push Notification Service refuses any notification that exceeds this limit.

这个很重要，payload，就是最后生成的那段Json，不得超过256字节。如果超过了，建议去掉一些不需要的参数，把alert，就是提示信息的字数减少

5.don’t repeatedly open and close connections. APNs treats rapid connection and disconnection as a denial-of-service attack.

6.If you send a notification that is accepted by APNs, nothing is returned.

发送成功的木有返回，只有发送失败的才会返回

7.If you send a notification that is malformed or otherwise unintelligible, APNs returns an error-response packet and closes the connection. Any notifications that you sent after the malformed notification using the same connection are discarded, and must be resent.

这条非常重要，如果有error-response，那么这条之后的通知都需要重发。有很多开源的库，在发苹果通知时都没有检测error-response，如果你不小心用了，那么用户很可能反馈“怎么没有通知啊”

8.The notification identifier in the error response indicates the last notification that was successfully sent（实际情况不是，实际上返回的是出错的那条通知的ID）. Any notifications you sent after it have been discarded and must be resent.When you receive this status code, stop using this connection and open a new connection.

这是对上一条的补充，如果出错了，需要关闭当前的连接，并且重新连接再发。error-response中返回的通知ID，可以帮助我们找出哪条出错了，这样就能知道哪些需要重发了

9.When a push notification cannot be delivered because the intended app does not exist on the device, the feedback service adds that device’s token to its list.

APNS的feedback service会返回那些已经卸载的设备的token--device_token。存储这些token，下次就不用再给他们发了，可以节省点资源。需要注意的是：feedback的接口读取一次，APNS就会清空它的列表，下次再读取时，返回的就是这两次读取之间这段时间新产生的device_token。

只有把这些搞清楚，才方便我们理解苹果推送的规则，知道自己推送上的一些不足之处。搞懂这些规则后，我自己封装了个Java的类库，已经开源并放到Github上了，下一篇文章奉上详情。

更多信息请查看IT技术专栏