Silent push notification

Im using keys for silent push notification. Server is able to send silent push notification locally when app is also running locally, but when pushed to AWS and app released to testflight its not able to send. Is there anything from APN to enable?

Answered by Engineer in 796660022

When you say

app released to testflight its not able to send.

do you mean you are receiving an error when sending the notification? Or are you trying to say the silent notifications are not reaching your app?

If you are getting an error, please share what the error code and message you are receiving from APNs is.

If the issue is that the silent pushes are not arriving at your app, then that is expected behavior.

The behavior you are seeing is expected, and it is due to content-available (aka "background" or "silent") push notifications being throttled when being delivered to apps that are in the background.

Background push notifications are never guaranteed to be delivered to the app every single time.

Additionally, notifications sent at low priority (priority 5) are throttled, regardless of payload. And background push notifications must always be sent at low priority. While you may expect up to several 1 or 2 push notifications per hour across all apps on a device, it is entirely possible and appropriate that you may receive none at all. Additionally, these notifications will not be delivered to the app at all if the user has not launched the app for a while.

The throttle is disabled if you run your app with a debugger attached. This allows you to test that your notifications are being received correctly, but should only be considered a best-case scenario.

The important point is that apps should never be designed expecting that every background push notification will be received. This is not how APNs is intended to work; it is intended to inform the user or app that some event of interest has occurred. Apps are expected to work properly, albeit perhaps with degraded functionality, if push notifications are not received. The user can turn off push notifications or background app updates at any time, and of course push notifications will not be received if the device doesn’t have network connectivity.

Also, an app will not be woken in the background by a push notification if the app had previously been force-quit. Force quit is considered a drastic choice by the user to say that they do not want the app to run, often because it misbehaved in some unrecoverable manner.


Argun Tekant /  DTS Engineer / Core Technologies

When you say

app released to testflight its not able to send.

do you mean you are receiving an error when sending the notification? Or are you trying to say the silent notifications are not reaching your app?

If you are getting an error, please share what the error code and message you are receiving from APNs is.

If the issue is that the silent pushes are not arriving at your app, then that is expected behavior.

The behavior you are seeing is expected, and it is due to content-available (aka "background" or "silent") push notifications being throttled when being delivered to apps that are in the background.

Background push notifications are never guaranteed to be delivered to the app every single time.

Additionally, notifications sent at low priority (priority 5) are throttled, regardless of payload. And background push notifications must always be sent at low priority. While you may expect up to several 1 or 2 push notifications per hour across all apps on a device, it is entirely possible and appropriate that you may receive none at all. Additionally, these notifications will not be delivered to the app at all if the user has not launched the app for a while.

The throttle is disabled if you run your app with a debugger attached. This allows you to test that your notifications are being received correctly, but should only be considered a best-case scenario.

The important point is that apps should never be designed expecting that every background push notification will be received. This is not how APNs is intended to work; it is intended to inform the user or app that some event of interest has occurred. Apps are expected to work properly, albeit perhaps with degraded functionality, if push notifications are not received. The user can turn off push notifications or background app updates at any time, and of course push notifications will not be received if the device doesn’t have network connectivity.

Also, an app will not be woken in the background by a push notification if the app had previously been force-quit. Force quit is considered a drastic choice by the user to say that they do not want the app to run, often because it misbehaved in some unrecoverable manner.


Argun Tekant /  DTS Engineer / Core Technologies

Accepted Answer

Hello, In the production mode aws is not able to send silent push notification successfully. The error is stream ended unexpectedly. Is there anything configuration to be done from app side, we are using tokens for registration.

Silent push notification
 
 
Q