APNS (Apple Push Notification Service) reliability

Our app uses APNS to receive Push Notifications. However, our client claims that some of their devices were not receiving notifications and argues to they ‘must’ make sure the notifications to be delivered 100%. But I have read somewhere that APNS is not 100% reliable and there should be cases which the notifications are not delivered.

I’m currently panic at how we could make sure APNS to received anytime. I have read that a case which may APNS not delivered (device may offline). But our test showing that even the device is online (Wifi or 3G), sometimes APNS were not delivered.

  • Open a specific tab/view when user receives a push notification
  • Swift read userInfo of remote notification
  • Change language of alert in banner of Push Notification
  • How to get back “Allow Push Notifications” dialog after it was dismissed once?
  • Open a view controller when a iOS push notification is received
  • How to catch all push notifications from other apps on iOS using private frameworks?
  • Is there any specific case which may APNS will not delivered? Or is there anything we (developers) can do with codes to make sure to receive all notifications? What I have done in the code is just registering the app to remote notification and write didRegisterForRemoteNotificationsWithDeviceToken, then throw the device token to our server.

    Any help would be appreciated, for our client almost kill us if ALL of their devices not receiving APNS!

    3 Solutions Collect From Internet About “APNS (Apple Push Notification Service) reliability”

    1. APNS is based on Apple Servers, and Apple doesn’t give any guarantee on successful message delivery.
    2. If the app is open (i.e. the user is using the app) while the notification arrives, iOS doesnt show a notification message, you need to handle it.
    3. Notification shows up only when the app is backgrounded or killed.
    4. Also implement feedback service on your server side; will help you get rid of old unwanted tokens(users who deleted the app or disabled notifications thru settings).
    5. Dont send too many notifications to a device within a short span of time, coz APNS caches only 1 message/device (if the device is offline). So it can deliver the message when the device comes online. Am not sure how long the message is cached though.

    Or just implement Pusher… http://pusher.com

    We’re facing the same problem. As everybody said, APNS is a best effort service so you can’t be sure every notification will be delivered, but what you can do is to be sure of which ones have been received. This is what we’re about to do. We register in our backend each notification que ship and the mobile app reports back each notification it receives. Then we set a maximum time of waiting for a notification to be received, if we don’t receive the report back we try again.

    I hope it might be helpful to someone (even 2 years later)

    It says it quite clearly in the Apple Docs that it is not 100% gauranteed and nor should it be used as so. Its sent with “best effort”.