v0.13.10 - iOS 13 updates

This release adds support for new apns-push-type header values and the target-content-id payload field introduced in iOS 13. For a complete list of changes, please see the v0.13.10 milestone.

v0.13.9 - iOS 13 updates and bug fixes

This release includes support for the new apns-push-type header introduced in (and required by) iOS 13/watchOS 6. It also includes a fix for an upstream issue where round-robin DNS resolvers wouldn't close the UDP ports they opened, leading to a leak.

For a complete list of changes, please see the v0.13.9 milestone.

v0.13.8 - Bug fixes!

This releases fixes a handful of bugs:

• We fixed an issue where notifications that were still buffered when a connection closed could wind up in "limbo," possibly leading to memory leaks. This would primarily affect users with some combination of high throughput or a bad network connection to the APNs server (which is frequently true in China).
• We fixed an issue where user-supplied tags weren't being added to some metrics in our Micrometer metrics listener.
• We rectified a misunderstanding about how Micrometer applies tags and updated docs and constructors to address the situation.
• We fixed an issue where we were identifying critical alerts with a boolean value, when it actually should have been a number.

For a complete list of changes, please see the v0.13.8 milestone.

v0.13.7 - Performance improvements and optional ALPN support for mock servers

This release includes a few small changes that yield major performance benefits for users whose throughput is primarily limited by processing time.

• Updated to Netty 4.1.32, which includes some under-the-hood improvements that give us a solid performance boost with no changes to Pushy itself (#658)
• Consolidated calls to flush(), which greatly reduces overhead when sending lots of notifications at the same time (#657)

Additionally, we re-introduced ALPN as an optional feature for mock servers (#656, #660). This is only really useful for folks who want to test non-Pushy clients against Pushy's mock server, and should have no adverse effects or system requirements for everybody else.

For a complete list of changes, please see the v0.13.7 milestone.

v0.13.6 - Payload properties for notification summaries

This is a minor release that adds support for the summary-arg and summary-arg-count payload fields, which allow notifications that get "stacked" on the receiving device to have custom summary strings (e.g. they can be used to change "4 more notifications" to, say, "4 more photos from Matt").

For a complete list of changes, please see the v0.13.6 milestone.

v0.13.5 - Fill the channel pool before reusing connections

This is a minor maintenance release that fixes a potential bug where ApnsClient instances may not create as many concurrent connections as expected under certain conditions. For details, please see the v0.13.5 milestone.

v0.13.4 - Minor leak fixes, better exception reporting

This is a minor maintenance release that addresses leaked UDP ports when closing ApnsClient instances and improves logging in cases where an attempt to send a push notification failed because the underlying network channel ultimately closed. For a complete list of changes, please see the v0.13.4 milestone.

v0.13.3 - Documentation updates, new sound dictionary, and better error reporting

This release updates documentation (and the payload builder) to keep up with recent upstream changes. The major changes in this release are:

• Updated documentation links to point at Apple's new UserNotifications framework docs instead of the now-deprecated Local and Remote Notification Programming Guide.
• Added support for the new sound dictionary to ApnsPayloadBuilder in order to support newly-introduced "critical notifications"
• Improved error handling to increase the chances that we'll have a more specific error message than "stream closed before a reply was received"

For a complete list of changes, please see the v0.13.3 milestone.

v0.13.2 - Dependency housekeeping

This release does not introduce any changes within Pushy itself, but does perform some dependency housekeeping. The most important change here is that netty-tcnative is no included as a dependency by default (because it is no longer actually required). Users who still want to use netty-tcnative will need to add it as a dependency to their projects separately.

For a complete list of changes, please see the v0.13.2 milestone.

v0.13.1 - Update to Netty 4.1.24

This release updates to Netty 4.1.24 as a dependency, which fixes an ugly-sounding upstream bug that caused Netty's resource cleanup code to halt. This release contains no changes to Pushy itself.