Logo Questions Linux Laravel Mysql Ubuntu Git Menu
HTML CSS JAVASCRIPT SQL PYTHON PHP BOOTSTRAP JAVA JQUERY R React Kotlin
 

iOS background push notifications not received after 2-3 hours of inactivity

Tags:

ios

push

background

notifications

My app performs silent background fetch via push notifications. Everything is working fine, and push notifications sent from our server trigger silent background fetches as expected, when the user has opened the app within the last 60 minutes or a push notification has been sent within 60 minutes - even if the device is locked.

However, when the user doesn't open the app for 2-3 hours or when a push notification hasn't been sent in 2-3 hours, the app isn't receiving the push notification. I have been logging app activity, and I've confirmed that:

didReceiveRemoteNotification:fetchCompletionHandler:

is not being called on the app delegate.

A few more facts:

  1. In the app's plist.info, I have set UIRequiresPersistentWiFi to true and UIBackgroundModes to (only) remote-notification
  2. The push notification payload contains only the content-available key
  3. After 2-3 hours of inactivity (either from no push notification sent or no user activity), I am seeing the same result on both my iPhone 5 and Wifi-only iPad 2, both running iOS 8.1.2. In other words, it doesn't matter whether the internet connection is cellular or Wifi.
  4. I don't believe I am hitting rate-limit boundaries, as I am only sending at most 1-2 push notifications per device per hour.

My understanding is that iOS should continue to wake the app up in the background and enable it to process the background fetch from the push notification - even after hours of inactivity (as long as the device is awake and has an internet connection).

I'm wondering if anyone else has experienced this, and if so, if you've found a workaround.

Thanks in advance!

like image 956
montuno Avatar asked Dec 16 '14 03:12

montuno

People also ask

Do push notifications work when app is closed iOS?

Apple does not offer a way to handle a notification that arrives when your app is closed (i.e. when the user has fully quit the application or the OS had decided to kill it while it is in the background). If this happens, the only way to handle the notification is to wait until it is opened by the user.

Does Apple throttle push notifications?

If you send too many, Apple Push Notification service (APNs) throttles your requests.

How long does a push notification last?

Push notifications should be kept short and simple. They should be instantly readable by the user. As a rule of thumb — push notifications should be around 60–90 characters for Android, and less than 120 characters for iOS.

How often should push notifications be sent?

As a rule of thumb, do not send more than 3-5 notifications every week. Even then, make sure that the notifications have something relevant for the user. Understand how users would use your app in their daily lives and identify opportunities to enhance that experience using push messages.

1 Answers

go through

Targets > Capabilities > Background Modes

Turn on Background Modes

like image 169
JayPathak Avatar answered Sep 18 '22 15:09

JayPathak
Sign in to Comment

Related questions

How can I monitor an application's API calls on a jailbroken iOS device?
Where to store API keys on Swift?
Is there any way stopping or pausing the execution of Javascript in a JSContext object?
Trouble with negating Core Data NSPredicate relationships
(iOS) iPad app Crashing Randomly on Start
appendSampleBuffer with an audio AVAssetWriterInput "leaks" memory until endSessionAtSourceTime
Mesh node location not updated, in cocos3d
Manually invoke state preservation in iOS 6 and onwards
Getting error on applying UDID as "Please enter a valid UDID"
UIPopover presentFromBarButton off center
When is Base.lproj used?

Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!