FCM background notifications not working in iOS

Question

I have a problem with FCM notification on iOS.

I receive notifications with success when my app is in foreground (the callback didReceiveRemoteNotification in appdelegate is fired), but I don't receive notifications when the app is in background (I do not see anything in the notification tray of iOS).

So, I think the problem is in the format of the message sent by FCM. The json sent by my server to FCM, is in the following format:

{  
   "data":{  
      "title":"mytitle",
      "body":"mybody",
      "url":"myurl"
   },
   "notification":{  
      "title":"mytitle",
      "body":"mybody"
   },
   "to":"/topics/topic"
}

As you can see, there are two blocks in my json: one notification block (to receive notifications in background), and one data block (to receive notifications in foreground).

I cannot understand why notifications in background are not received. My doubts are about the order of the blocks (is a problem if I put the "data" block before the "notification" block?).

EDIT: More info about the problem.

This is my appdelegate.swift:

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate
{
    var window: UIWindow?


    // Application started
    func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject : AnyObject]?) -> Bool
    {
        let pushNotificationSettings: UIUserNotificationSettings = UIUserNotificationSettings(forTypes: [.Alert, .Badge, .Sound], categories: nil)
        application.registerUserNotificationSettings(pushNotificationSettings)
        application.registerForRemoteNotifications()

        FIRApp.configure()

        NSNotificationCenter.defaultCenter().addObserver(self, selector: "tokenRefreshNotification:", name: kFIRInstanceIDTokenRefreshNotification, object: nil)

        return true
    }




    // Handle refresh notification token
    func tokenRefreshNotification(notification: NSNotification) {
        let refreshedToken = FIRInstanceID.instanceID().token()
        print("InstanceID token: \(refreshedToken)")

        // Connect to FCM since connection may have failed when attempted before having a token.
        if (refreshedToken != nil)
        {
            connectToFcm()

            FIRMessaging.messaging().subscribeToTopic("/topics/topic")
        }

    }


    // Connect to FCM
    func connectToFcm() {
        FIRMessaging.messaging().connectWithCompletion { (error) in
            if (error != nil) {
                print("Unable to connect with FCM. \(error)")
            } else {
                print("Connected to FCM.")
            }
        }
    }


    // Handle notification when the application is in foreground
    func application(application: UIApplication, didReceiveRemoteNotification userInfo: [NSObject : AnyObject], fetchCompletionHandler completionHandler: (UIBackgroundFetchResult) -> Void) {
            // If you are receiving a notification message while your app is in the background,
            // this callback will not be fired till the user taps on the notification launching the application.
            // TODO: Handle data of notification

            // Print message ID.
            print("Message ID: \(userInfo["gcm.message_id"])")

            // Print full message.
            print("%@", userInfo)
    }


    // Application will enter in background
    func applicationWillResignActive(application: UIApplication)
    {
        // Sent when the application is about to move from active to inactive state. This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message) or when the user quits the application and it begins the transition to the background state.
        // Use this method to pause ongoing tasks, disable timers, and throttle down OpenGL ES frame rates. Games should use this method to pause the game.
    }



    // Application entered in background
    func applicationDidEnterBackground(application: UIApplication)
    {
        FIRMessaging.messaging().disconnect()
        print("Disconnected from FCM.")
    }



    // Application will enter in foreground
    func applicationWillEnterForeground(application: UIApplication)
    {
        // Called as part of the transition from the background to the active state; here you can undo many of the changes made on entering the background.
    }



    // Application entered in foreground
    func applicationDidBecomeActive(application: UIApplication)
    {
        connectToFcm()

        application.applicationIconBadgeNumber = 0;
    }



    // Application will terminate
    func applicationWillTerminate(application: UIApplication)
    {
        // Called when the application is about to terminate. Save data if appropriate. See also applicationDidEnterBackground:.
    }


}

The only way I can receive messages in foreground, is by disabling method swizzling, setting FirebaseAppDelegateProxyEnabled to NO in my info.plist.

In this case, FCM documentation says that I have to implement in my appdelegate.swift two methods:

 - FIRMessaging.messaging().appDidReceiveMessage(userInfo)  in didReceiveRemoteNotification callback
 - FIRInstanceID.instanceID().setAPNSToken(deviceToken, type: FIRInstanceIDAPNSTokenType.Sandbox) in didRegisterForRemoteNotificationsWithDeviceToken callback

But if I implement those functions, messages stops to arrive even when the app is in foreground.

I know this is very strange.

EDIT 2:

When the app is in background the notification isn't received, but when i open my app, the same notification is received immediately (method didReceiveRemoteNotification is fired).

Cellulous

Just out of interest, did you try to set the priority to high? – Chaw

yes, but nothing changed. still no notifications in background. – Oxazine

Try adding content_available with true value. If it doesn't work, try removing priority while using content_available. I'm not so familiar on how APNS works, but there's a chance that the message will be ignored if both priority and content_available is in a single payload. Let me know if it works. Cheers! – Tilla

Have you tried it out @MarkO'Brian? Did it work? – Tilla

i am the same problem ! fcm don't send the message to apns – Syphilology

I had the same problem, but I already have the priority set to High and this did not help – Mahout

setting the priority to high didn't help me either. I do get foreground messages, and background messages work on Android, just not iOS. Not sure what's going on – Fluter

@astromme did you get this working? – Raleigh

@Raleigh Yes! I needed to add the push notification entitlement. I did this by my target settings in Xcode, then Capabilities, then turned on "Push Notifications" – Fluter

@RyanCocuzzo try my answer https://mcmap.net/q/296808/-fcm-background-notifications-not-working-in-ios which fixed the issue for me. Does that work for you? – Fluter

@astromme I had that enabled already but thanks – Raleigh

Answer 1

Assuming you've set up everything correctly, then setting the priority of the message from normal to high should make it appear immediately. This is due to the way iOS bundles notifications and handles them. You can read about the Priority of FCM notifications here. Please note that you shouldn't really use high in production unless there is a good case for it, as it has a battery penalty.

Here is the reference from Apple's docs

The priority of the notification. Specify one of the following values:

10–Send the push message immediately. Notifications with this priority must trigger an alert, sound, or badge on the target device. It is an error to use this priority for a push notification that contains only the content-available key.

5—Send the push message at a time that takes into account power considerations for the device. Notifications with this priority might be grouped and delivered in bursts. They are throttled, and in some cases are not delivered. If you omit this header, the APNs server sets the priority to 10.

Chaw

hi, thank you for your answer! Assuming that this is the problem, what should i have to do to receive background notifications in production mode without setting priority to high? – Oxazine

You just wait for it to appear. iOS decides when to display it. See my updated answer – Chaw

ok, it seems legit.. but what about messages i've sent 2 hours ago and not arrived yet? i mean, those are messages sent through a development APNS certificate, not production. Is there a difference in terms of forwarding time between development messages and production messages? – Oxazine

Assuming that you have set it all up correctly, then you should definately be seing them sooner than that. But consider that when you send a notification to your app when it's in the background and you don't see it showing up, then opening up the app, then that notification fires immediately and is no longer in the queue. Makes sense? As I said, this is all assuming that you have followed Firebase's guide on how to it up for bg notifications correctly and it works as it should. You haven't provided much code to verify that, so I made some strong assumptions in my answer – Chaw

hi, i've updated my question with more code and details - thank you! – Oxazine

Thanks! We were having the same issue and it turns out that priority high fixed it. Without a priority none of them were coming in while in the background. – Brannon

I can confirm that the problem was the priority. After I set priority to high, my problem has solved. Thank you guys! – Oxazine

@MarkO'Brian can you send me the payload json. I am not getting proper format of json to send notification using FCM. – Wheelsman

@MarkO'Brian can you give us an example of working code for background ios push ? – Kalif

Answer 2

You need to set the content_available property to true like so:

{  
   "data":{  
      "title":"mytitle",
      "body":"mybody",
      "url":"myurl"
   },
   "notification":{  
      "title":"mytitle",
      "body":"mybody",
      "content_available": true
   },
   "to":"/topics/topic"
}

There is a blue note box on in this section that states this: https://firebase.google.com/docs/cloud-messaging/concept-options#notifications

Sacerdotalism

This answer is important for whom, like me, forgot to put the "notification" object. – Laughable

From firebase.google.com/docs/cloud-messaging/http-server-ref, the content_available key should be in the same level as data, notification, to, and not inside notification. – Minium

@Minium when I put content_available : 1 at the same level as data, I get the error: <FIRMessaging/WARNING> FIRMessaging receiving notification in invalid state 2, When I use content-aavailable : 1, I no longer get a warning, either way, I am getting the notifications in the tray and they are not silent. Any ideas? – Raleigh

@Raleigh content_available should be true instead of 1 due to how Firebase Messaging processes the object. content_available is for GCM, content-available is for APNS. – Jugate

Thanks, this format helped me a lot in making a notification that works for both Android and iOS. – Filmer

Thank you sooo much. You saved my life. – Solfatara

Answer 3

Priority and content_available (as mentioned in other answers) are the key elements to make sure you receive the notifications. Tests showed interesting results, so I thought to share them here.

Test Results: Swift 3, Xcode 8, iOS 10

Priority = "high" => "immediate" (within obvious network delays) reception of message.

Priority = "normal" => various results (generally fast, though obviously slower than "high")

content_available = true in the notifications (no payload message)

• Foreground = data received as expected
• Background = data received as expected (when opening the app)

content_available = true in the top level (no payload message)

• Foreground = data received as expected
• Background = data received as expected (when opening the app)

content_available = true in the notifications (with message {title/body})

• Foreground = data received TWICE
• Background = data received TWICE (when opening the app)

content_available = true in the top level (with payload message)

• Foreground = data received TWICE
• Background = data received TWICE (when opening the app)

CONCLUSIONS:

1. While Priority is a possible cause of not receiving messages, the MOST IMPORTANT factor is that you must have either 'content_available' or a payload message.
2. content_available MUST be used on data-only payloads (without it, no message is ever sent).
3. content_available SHOULD NOT be used on payloads that contain messages as it causes double messages to be sent from FCM.
4. No difference found in the use of content_available in the top level or in the notifications.

EDIT: Additional testing results: - if you have a msg title you MUST have a msg body or you don't get an alert.

The odd part of this is that you WILL get the vibrate, badge and sound, but the alert box won't show up unless you have a body as well as the title.

Crosier

Answer 4

You might need to add the push notification entitlement. Do this by going to your target settings, then clicking "Capabilities" and turning "Push Notifications" on.

Fluter

Answer 5

-For FCM when application is in background or foreground and OS <10 application(_:didReceiveRemoteNotification:) method will fire.

-When application is foreground and OS => 10 userNotificationCenter:willPresentNotification:withCompletionHandler: method will fire.

-When sending data message without notification component: application(_:didReceiveRemoteNotification:) method will fire.

-When sending data message with notification component : userNotificationCenter:willPresentNotification:withCompletionHandler: method will fire.

Lipetsk

from Firebase documentation, is it not the func messaging(_ messaging: Messaging, didReceive remoteMessage: MessagingRemoteMessage) that has to be called instead of application(_:didReceiveRemoteNotification:) for direct messages? – Sheridan

Answer 6

I had this issue, with the content_available property set. The solution was to remove and reinstall the application from the iOS device.

Potemkin

What is this, where?? – Lincoln