10 min read
Push notifications with APNs: the path from token to delivery
The APNs path from token registration to delivery, including payload limits, collapse behavior, and diagnosing silent failures.
Read the essayEnteror double click opens it
Topics
In this essay
- 1. The whole path in one pass
- 2. A token identifies an install, not a person
- 3. Tokens rotate, and the table has to admit it
- 4. Authenticate with a key, not a certificate
- 5. The headers decide what happens to the message
- 6. The payload is 4 KB, and that is the whole budget
- 7. Collapse IDs and the notifications you should not send
- 8. Background pushes have their own rules
- 9. When APNs says no
- 10. Delivered is not the same as visible
- 11. What to instrument
- 12. Test the parts the simulator cannot test
- 13. Treat it as an interruption budget