2

Is it possible to receive a silent push notification ("content-available": "1") and run a function to change data in NSUserDefaults.standardUserDefaults() without the user having to tap the notification (there is no notification in the notification center, since it's a silent push notification). The app is not running at all (e.g. force-quit by user). I have tried the code below and it worked if the app was running or in the background, but I also want it to work if the app was force-quit (not running at all).

I have enabled background fetch and remote notifications.

func application(application: UIApplication, didReceiveRemoteNotification userInfo: [NSObject : AnyObject], fetchCompletionHandler completionHandler: (UIBackgroundFetchResult) -> Void) {
    handleNotification()
}

//this works, the someData is not a problem
func handleNotification() -> Void{
    let defaults = NSUserDefaults.standardUserDefaults()
    defaults.setValue(someData, forKey: "key")
    defaults.synchronize()
}

When I send push notifications, if the app is active or in background, the data is updated, but if the app is not running at all, the data is not updated.

Baris Akar
  • 4,895
  • 1
  • 26
  • 54
user5132182
  • 31
  • 1
  • 3
  • I wrote : i have the background fetch and remote notifications enabled. in the capabilities- background modes i checked them both – user5132182 Jul 19 '15 at 12:48
  • I take everything back :( – luk2302 Jul 19 '15 at 12:48
  • well, is it possible to do such thing ? – user5132182 Jul 19 '15 at 12:49
  • As far as I understand the docs, yes. Have not tried so far though – luk2302 Jul 19 '15 at 12:49
  • This does work if the notification is not silent and the user clicks on the notification bar, but if he does not click on the notification bar the function is not called. – user5132182 Jul 19 '15 at 12:54
  • 2
    Have you force-quit the application previously? As far as I understand the docs you must not do that: "In addition, if you enabled the remote notifications background mode, the system launches your app (or wakes it from the suspended state) and puts it in the background state when a remote notification arrives. However, the system does not automatically launch your app if the user has force-quit it" – luk2302 Jul 19 '15 at 12:58
  • possible duplicate of [Will iOS launch my app into the background if it was force-quit by the user?](http://stackoverflow.com/questions/19068762/will-ios-launch-my-app-into-the-background-if-it-was-force-quit-by-the-user) – Baris Akar Jul 20 '15 at 11:56

1 Answers1

1

Short answer: There is (almost) no way to do anything without user interaction, when the app was force-quit (is not running).

For explanation see the documentation:

  • Handling Remote Notifications - application:didReceiveRemoteNotification:fetchCompletionHandler:

    Use this method to process incoming remote notifications for your app. Unlike the application:didReceiveRemoteNotification: method, which is called only when your app is running in the foreground, the system calls this method when your app is running in the foreground or background. In addition, if you enabled the remote notifications background mode, the system launches your app (or wakes it from the suspended state) and puts it in the background state when a remote notification arrives. However, the system does not automatically launch your app if the user has force-quit it. In that situation, the user must relaunch your app or restart the device before the system attempts to launch your app automatically again.

  • Understanding When Your App Gets Launched into the Background:

    Apps that support background execution may be relaunched by the system to handle incoming events. If an app is terminated for any reason other than the user force quitting it, the system launches the app when one of the following events happens:

    • For location apps: The system receives a location update that meets the app’s configured criteria for delivery. The device entered or exited a registered region. (Regions can be geographic regions or iBeacon regions.)
    • For audio apps, the audio framework needs the app to process some data. (Audio apps include those that play audio or use the microphone.)
    • For Bluetooth apps: An app acting in the central role receives data from a connected peripheral. An app acting in the peripheral role receives commands from a connected central.
    • For background download apps: A push notification arrives for an app and the payload of the notification contains the content-available key with a value of 1. The system wakes the app at opportunistic moments to begin downloading new content.
    • For apps downloading content in the background using the NSURLSession class, all tasks associated with that session object either completed successfully or received an error. A download initiated by a Newsstand app finishes. In most cases, the system does not relaunch apps after they are force quit by the user.

    One exception is location apps, which in iOS 8 and later are relaunched after being force quit by the user. In other cases, though, the user must launch the app explicitly or reboot the device before the app can be launched automatically into the background by the system.

As you see, only exception are location apps, but this won't help you. Just deal with the fact, that this is an OS limitation and you can't do anything about it.

Baris Akar
  • 4,895
  • 1
  • 26
  • 54