33 releases

0.10.0 May 5, 2024
0.8.1 Apr 25, 2024
0.8.0 Aug 29, 2023
0.7.1 Jun 5, 2023
0.3.3 Jun 26, 2018

#214 in Cryptography

Download history 165/week @ 2024-01-31 86/week @ 2024-02-07 117/week @ 2024-02-14 262/week @ 2024-02-21 218/week @ 2024-02-28 204/week @ 2024-03-06 194/week @ 2024-03-13 162/week @ 2024-03-20 162/week @ 2024-03-27 237/week @ 2024-04-03 211/week @ 2024-04-10 401/week @ 2024-04-17 675/week @ 2024-04-24 394/week @ 2024-05-01 302/week @ 2024-05-08 489/week @ 2024-05-15

1,917 downloads per month
Used in xorc-notifications

MIT license

100KB
1.5K SLoC

a2

CI Status MIT licensed crates.io docs.rs

HTTP/2 Apple Push Notification Service for Rust using Tokio and async sending.

Requirements

Needs a Tokio executor version 1.0 or later and Rust compiler version 1.60.0 or later.

Features

  • Fast asynchronous sending, based on h2 and hyper crates.
  • Payload serialization/deserialization with serde.
  • Provides a type-safe way of constructing different types of payloads. Custom data through Serialize, allowing use of structs or dynamic hashmaps.
  • Supports .p12 certificate databases to connect using a custom certificate.
  • Supports .p8 private keys to connect using authentication tokens.
  • If using authentication tokens, handles signature renewing for Apple's guidelines and caching for maximum performance.
  • Cryptography primitives are provided either by openssl or ring.

Examples

The library supports connecting to Apple Push Notification service either using a certificate with a password or a private key with a team id and key id. Both are available from your Apple account and with both it is possible to send push notifications to one application.

To see it used in a real project, take a look to the Echo Server, which is a project by WalletConnect to handle incoming webhooks and converting them to push notifications.

Gotchas

We've been pushing some millions of notifications daily through this library and are quite happy with it. Some things to know, if you're evaluating the library for production use:

  • Do not open new connections for every request. Apple will treat it as Denial of Service attack and block the sending IP address. When using the same Client for multiple requests, the Client keeps the connection alive if pushing steady traffic through it.

  • For one app, one connection is quite enough already for certain kind of loads. With http2 protocol, the events are asynchronous and the pipeline can hold several outgoing requests at the same time. The biggest reason to open several connections is for redundancy, running your sender service on different machines.

  • It seems to be Apple doesn't like when sending tons of notifications with faulty device tokens and it might lead to ConnectionErrors. Do not send more notifications with tokens that return Unregistered, BadDeviceToken or DeviceTokenNotForTopic.

Tests

cargo test

Dependencies

~18–28MB
~509K SLoC