Here at Indiespring we closely observe the changes being made throughout the year by Android and iOS to make sure our client’s apps are compliant and take advantage of the new features that become part of these ecosystems. We have published a few articles on the changes made in iOS 13 but one may have flown under the radar and has left many people scratching their heads.

Push notifications are used by many apps to remarket and engage their users. They are proven to increase conversion rates compare to generic email marketing with around 3 times better “click” through rate. Users that have push notifications enabled also open apps 3 times more often than those without; so you can see how powerful they can be. However many apps are being caught out with a subtle change in iOS 13 regarding push notifications.

Unless your developers have been keeping a close eye on push notification policies the chances are that your push notifications have stopped working as they did. At WWDC Appleran some sessions to demonstrate how the behaviours were going to change but there are still contradictions in their documentation. Make sure you get this tested to ensure you are following the correct guidelines.


What you Need to Know

In short your development team need to update their use of attributes to align themselves with Apple’s new guidelines. Also updates which only pertain to newly released content will now be delivered less frequently. Lastly, if you’re still using TLS 1 for your server communications then you need to update ASAP to avoid being locked out completely. For a great technical writeup head over to or call us and we can walk you through the details.

If your development team haven’t done any or all of the above, you may find your push notification delivery rate and time drop significantly or, at worst, push notifications may fail to be delivered at all. It’s best to check as these changes were only quietly rolled out so if you’re in any doubt – reach out!.