#node-apn
A Node.js module for interfacing with the Apple Push Notification service.
- Fast
- Maintains a connection to the server to maximise notification batching and throughput.
- Enhanced binary interface support, with error handling
- Automatically sends unsent notifications if an error occurs
- Feedback service support
- Complies with all best practises laid out by Apple
Via npm:
$ npm install apn
As a submodule of your project (you will also need to install q)
$ git submodule add http://github.com/argon/node-apn.git apn
$ git submodule update --init
This is intended as a brief introduction, please refer to the documentation in doc/ for more details.
var apn = require('apn');
- Connection
- Notification
- Device
- Feedback
- Errors
Create a new connection to the APN gateway server using a dictionary of options. If you name your certificate and key files appropriately (cert.pem and key.pem) then the defaults should be suitable to get you up and running, the only thing you'll need to change is the gateway if you're in the sandbox environment.
var options = { "gateway": "gateway.sandbox.push.apple.com" };
var apnConnection = new apn.Connection(options);Important: In a development environment you must set gateway to gateway.sandbox.push.apple.com.
To send a notification first create a Device object. Pass it the device token as either a hexadecimal string, or alternatively as a Buffer object containing the token in binary form.
var myDevice = new apn.Device(token);
Next, create a notification object and set parameters. See the payload documentation for more details.
var note = new apn.Notification();
note.expiry = Math.floor(Date.now() / 1000) + 3600; // Expires 1 hour from now.
note.badge = 3;
note.sound = "ping.aiff";
note.alert = "\uD83D\uDCE7 \u2709 You have a new message";
note.payload = {'messageFrom': 'Caroline'};
apnConnection.pushNotification(note, myDevice);
The above options will compile the following dictionary to send to the device:
{"messageFrom":"Caroline","aps":{"badge":3,"sound":"ping.aiff","alert":"\uD83D\uDCE7 \u2709 You have a new message"}}
If you wish to send notifications containing emoji or other multi-byte characters you will need to ensure they are encoded correctly within the string. Notifications can be transmitted to Apple in either UTF-8 or UTF-16 and strings passed in for the Alert will be converted accordingly. UTF-8 is recommended for most cases as it can represent exactly the same characters as UTF-16 but is usually more space-efficient. When manually encoding strings as above with \uD83D\uDCE7 the character (in this case a surrogate pair) is escaped in UTF-16 form because Javascript uses UTF-16 internally for Strings but does not handle surrogate pairs automatically.
If in doubt, leave the encoding as default. If you experience any problems raise an issue on GitHub.
Apple recommends checking the feedback service periodically for a list of devices for which there were failed delivery attempts.
Using the Feedback object it is possible to periodically query the server for the list. Many of the options are similar to that of Connection.
Attach a listener to the feedback event to receive the output as two arguments, the time returned by the server (epoch time) and a Buffer object containing the device token - this event will be emitted for each device separately. Alternatively you can enable the batchFeedback option and the feedback event will provide an array of objects containing time and device properties.
var options = {
"batchFeedback": true,
"interval": 300
};
var feedback = new apn.Feedback(options);
feedback.on("feedback", function(devices) {
devices.forEach(function(item) {
// Do something with item.device and item.time;
});
});
By specifying a time interval (in seconds) Feedback will periodically query the service without further intervention.
Important: In a development environment you must set address to feedback.sandbox.push.apple.com.
More information about the feedback service can be found in the feedback service documentation.
After requesting the certificate from Apple, export your private key as a .p12 file and download the .cer file from the iOS Provisioning Portal.
Now, in the directory containing cert.cer and key.p12 execute the following commands to generate your .pem files:
$ openssl x509 -in cert.cer -inform DER -outform PEM -out cert.pem
$ openssl pkcs12 -in key.p12 -out key.pem -nodes
If you are using a development certificate you may wish to name them differently to enable fast switching between development and production. The filenames are configurable within the module options, so feel free to name them something more appropriate.
It is also possible to supply a PFX (PFX/PKCS12) package containing your certificate, key and any relevant CA certificates. The method to accomplish this is left as an exercise to the reader. It should be possible to select the relevant items in "Keychain Access" and use the export option with ".p12" format.
If you experience difficulties sending notifications or using the feedback service you can enable debug messages within the library by running your application with DEBUG=apn or DEBUG=apnfb set as an environment variable.
You will need the debug module which can be installed with npm install debug.
You are encouraged to read the extremely informative Troubleshooting Push Notifications Tech Note in the first instance, in case your query is answered there.
If you experience any difficulties please create an Issue on GitHub and if possible include a log of the debug output around the time the problem manifests itself. If the problem is reproducible sample code is also extremely helpful.
- Local and Push Notification Programming Guide: Apple Push Notification Service
- Apple Technical Note: Troubleshooting Push Notifications
- List of Projects, Applications and Companies Using Node-apn
Written and maintained by Andrew Naylor.
Thanks to: Ian Babrou, dgthistle, Keith Larsen, Mike P, Greg Bergé, Asad ur Rehman, Nebojsa Sabovic, Alberto Gimeno, Randall Tombaugh, Michael Stewart, Olivier Louvignes, porsager, Craig Hockenberry
Released under the MIT License
Copyright (c) 2010 Andrew Naylor
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.