Apns tools

This tool is not meant for production usage There are many production-ready options for interacting with APNs that offer cross-platform notifications, advanced device management, and multi-targeting.

Add support for saving credentials. Add support for reading the --data value from stdin. Add support for arbitrary apns- headers. MIT License. Releases No releases published. Packages 0 No packages published.

You signed in with another tab or window. Reload to refresh your session. A canonical UUID that identifies the notification. If there is an error sending the notification, APNs uses this value to identify the notification to your server. The canonical form is 32 lowercase hexadecimal digits, displayed in five groups separated by hyphens in the form An example UUID is as follows:.

This header identifies the date when the notification is no longer valid and can be discarded. If this value is nonzero, APNs stores the notification and tries to deliver it at least once, repeating the attempt as needed if it is unable to deliver the notification the first time. If the value is 0 , APNs treats the notification as if it expires immediately and does not store the notification or attempt to redeliver it.

Notifications with this priority must trigger an alert, sound, or badge on the target device. It is an error to use this priority for a push notification that contains only the content-available key. Notifications with this priority might be grouped and delivered in bursts. They are throttled, and in some cases are not delivered. If you omit this header, the APNs server sets the priority to The topic of the remote notification, which is typically the bundle ID for your app.

The certificate you create in your developer account must include the capability for this topic. If your certificate includes multiple topics, you must specify a value for this header. If you are using a provider token instead of a certificate, you must specify a value for this request header. The topic you provide should be provisioned for the your team named in your developer account.

Multiple notifications with the same collapse identifier are displayed to the user as a single notification. The value of this key must not exceed 64 bytes. The body data must not be compressed and its maximum size is 4KB bytes. For information about the keys and values to include in the body content, see Payload Key Reference.

The response to a request has the format listed in Table The apns-id value from the request. If no value was included in the request, the server creates a new UUID and returns it in this header.

The HTTP status code. For a list of possible status codes, see Table Table lists the possible status codes for a request. These values are included in the :status header of the response. There was an error with the certificate or with the provider authentication token. The request used a bad :method value. Only POST requests are supported. For a successful request, the body of the response is empty.

The error indicating the reason for the failure. The error code is specified as a string. For a list of possible values, see Table If the value in the :status header is , the value of this key is the last time at which APNs confirmed that the device token was no longer valid for the topic.

Stop pushing notifications until the device registers a token with a later timestamp with your provider. The specified device token was bad. Latest commit. Git stats 4 commits. Failed to load latest commit information.

View code. The tools currently provided are described below. Two elliptic curve private keys for testing APNS token-based authentication. Releases No releases published.