Release 2.1.0

Wed 09 March 2016 by Misha Nasledov

Please check out our release notes for version 2.1.0.

New APIs have been added: one for listing the subscriptions of a subscriber and another for showing the configurations of the push service providers for services that exist.

Concurrency issues in ADM and APNS have been fixed. The APNS implementation has been changed to use a new, reliable worker pool implementation.

This implementation has been running reliably at production scale, at a company named if(we), sending push notifications for the Tagged and hi5 social networks for a while now (nearly a year at time of writing). The company has 12 processes handling a peak of 60 APNS push notifications per second, and the tier is overprovisioned in order to be able to deal with traffic increases and potential surges. That's about 5 APNS push notifications per process per second. In addition, if(we) sends about 270 GCM push notifications per second distributed amongst these same processes, which adds about another 22 GCM push notifications per second each process sends. The subscribe API on the tier ends up getting hit about 500 times per second (about 42 queries per process per second). So, each process is handling about 70 queries a second easily. if(we) has been running without any issues for many months, especially after fixing some bugs that eventually manifested only at their scale.

A bug which could lead to infinite loops in rare circumstances has been fixed.

The APNS implementation no longer uses Go's default HTML escaping of JSON payloads. The APNS servers now render payloads with characters such as '"' properly.

More details have been added to error messages so that problems can be debugged more easily.

The APNS implementation has also been updated to deal with 100-byte APNS device tokens (previously 32-bytes) which Apple said it would roll out in 2016.


Release 2.0.0

Tue 08 March 2016 by Misha Nasledov

Please check out our release notes for version 2.0.0.

We've improved the response format of most APIs. Instead of sending server logs back, they now return JSON response objects. This makes it easy to distinguish successes from failures. For example, when sending push notifications to a subscriber ...

read more

Release 1.5.2

Sun 29 June 2014 by Monnand

TL;DR: Please checkout our release note for version 1.5.2.

Sorry for my absence since November 2013. I was preparing other things and working on other projects. During this period, I received several bug reports related to uniqush-push. Some of them indicating some large service is currently using ...

read more

Release 1.5.1

Sat 09 November 2013 by Monnand

This version contains several minor bug fixes and improvements. Details can be found in the release note. Two noticeable changes are:

  • Subscriber and service names can contain @ now.
  • content-available parameter is supported in APNS.
read more

Release 1.5.0: Kindle Support

Sun 01 September 2013 by Monnand

I'm very glad to announce that uniqush supports ADM since version 1.5.0, which means users can use it to push notifications to Amazon Kindle Tablets.

This is the only change in this version and since it changed the user interface, it is considered as a big change ...

read more

Release 1.4.5

Thu 01 August 2013 by Monnand

This version contains only one bug fix. Since this bug is critical, it is highly recommended to upgrade to this version.

Thanks for cmabastar-gumi's bug report again. For more details, please check out our release note.

read more

Release 1.4.4

Sat 20 July 2013 by Monnand

This version contains some minor bug fixes and a huge improvement for APNS. I would like to give special thanks to cmabastar-gumi for his detailed bug reports. Please check the release note for detailed ChangeLog.

In this post, I will explain more about how I improved the performance for APNS ...

read more