Geek Answers Handbook

Remote notification does not start the application in the background

I started experimenting with the new remote notification service in iOS 7. An interesting part from the documentation is the UIApplication delegate protocol .

If your application is paused or not running, the system wakes up or starts your application and puts it in the background working state before calling the method.

However, when I send a quiet remote notification with the key "available content" and payload "1", the application does not start in the background. If my application is in the background or paused, a notification is delivered to the application.

Incorrect documentation?

+4
source share
2 answers

The Apple doc is a bit confusing when it comes to remote notifications.
If your application was interrupted by the user or your device was rebooted, a notification will not be delivered.

"content-accessible" only wakes up your application if it was in the background or the application was killed by the system due to memory pressure.

0
source

Add / update documentation as I totally agree with Guatam Jain. The strength of the exit is what threw me - Apple cannot distinguish the difference between the developer performing the test and the user “cleaning his phone” or manipulating the wrong application.

https://developer.apple.com/library/content/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/BackgroundExecution/BackgroundExecution.html, " , " ( ):

, , . - , , , , :... : push-, , , 1.

0

More articles:


All Articles