didReceiveRemoteNotification not called in iOS 13.3 when app is in background

I am banging my head. I am implementing push notification. Everything is working fine (push is received, badge is updated) but under iOS 13.3 the method application(_:didReceiveRemoteNotification:fetchCompletionHandler:) is not called when the app is in the background. If the app is in the foreground or using an iOS 12 device the method is called. I register for push notification in the following way (yes, it is still Objective C)


[[UNUserNotificationCenter currentNotificationCenter] requestAuthorizationWithOptions:(UNAuthorizationOptionBadge | UNAuthorizationOptionSound | UNAuthorizationOptionAlert) completionHandler:^(BOOL granted, NSError * _Nullable error) {
  if (granted) {
  dispatch_async(dispatch_get_main_queue(), ^{
  [[UIApplication sharedApplication] registerForRemoteNotifications];
  });
  }
}];


The payload is set to the following:


{"aps": {
  "badge": 10,
  "alert": "test",
  "content-available": 1
}}


I tried adding "Remote notifications" and "Background processing" as app capabilities in all variations (only "Remote notifications"/"Background processing", without any of those capabilities, enabling both) without any change. I set the delegate for the UNUserNotificationCenter but again without success. I set the headers accordingly:


curl -v \
 -H 'apns-priority: 4' \
 -H 'apns-topic: xx.xxxxx.xxxx' \
 -H 'apns-push-type: alert' \
 -H 'Content-Type: application/json; charset=utf-8' \
 -d '{"aps": {"badge": 10,"alert": "test", "content-available":1}}' \
 --http2 \
 --cert pushcert.pem \
 https://api.sandbox.push.apple.com/3/device/1234567890


From the docs it states that this method is called even when the app is in background:


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.


I tried with and without background modes (Remote Notification, Background processing, Background fetch) but without success. If I use an iOS 12 device, the method is called.


My goal is to process some of the information in the payload (there might be additional information).

What am I missing here for iOS 13 (13.3 to be exact)?

Up vote post of martinw1974 Down vote post of martinw1974
18k views
Posted by
martinw1974
Reply
Add a Comment

Replies

I'm facing the same issue. Please let me know if you were able to figure it out.

Posted by
preema22
Up vote reply of preema22 Down vote reply of preema22
Add a Comment

I am also facing the same issue. Does anyone solved this issue. I get call back when app is in the foreground and when user clicks on push notification to

didReceiveRemoteNotification

Please let me know If anyone has solution.

Posted by
ajith_8291
Up vote reply of ajith_8291 Down vote reply of ajith_8291
Add a Comment

In my case, the solution was: move the super call to the beginning of didFinishLaunchingWithOptions method implementation


- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  [super application:application didFinishLaunchingWithOptions:launchOptions];
  …
  return YES;
}
Posted by
rephaim
Up vote reply of rephaim Down vote reply of rephaim
Add a Comment
Facing the same issue on iOS 14.0.1
Posted by
fembrioni
Up vote reply of fembrioni Down vote reply of fembrioni
Add a Comment
I am facing the same issue in 13.3, can you tell me the solution if you have done.
Posted by
Riyasat_ali
Up vote reply of Riyasat_ali Down vote reply of Riyasat_ali
Add a Comment
I can't believe this is still not answered.
Can anyone handle silent notifications with firebase on iOS 14 using swift?
Posted by
SlobodanMargetic988
Up vote reply of SlobodanMargetic988 Down vote reply of SlobodanMargetic988
Add a Comment
Still anyone got solution ?
Posted by
muhammadwasim
Up vote reply of muhammadwasim Down vote reply of muhammadwasim
Add a Comment

What worked for me in iOS 14 is adding "content-available": "true"

Posted by
spendingmouse
Post not yet marked as solved Up vote reply of spendingmouse Down vote reply of spendingmouse

  • not allowing me to send "content-available": "true", Is this working for you?

    —
    sathish_kondi

  • Try this sample payload.

    {

    "aps": { "alert":  "Game Request", 

    "sound": "default",

    "content-available": 1

    }

    }

    —
    ravi46kumar
Add a Comment

Try explicitly setting "content-available" to 1 (integer) (as noted by many others), leave out the alert key, AND the sound entry to an empty string. That made the difference for me, after a rather exhaustive diagnostic session. I was omitting the sound entry and it never worked. I tried setting a sound file name and it never worked. Setting it to an empty string ( "" ) worked fine when accompanied by content-available and omitting the alert key.

Printing what I receive (as seen below with my various diagnostic print statements) showed: ["sound": , "content-available": 1, "badge": 0]

        guard let aps = userInfo["aps"] as? [String: AnyObject] else {
            print( "Incoming failed" )
            completionHandler(.failed)
            return
        }

        print( aps )
        print( "INCOMING" )
Posted by
chornbe
Post not yet marked as solved Up vote reply of chornbe Down vote reply of chornbe
Add a Comment

I was struggling with this problem.

However, it disappears after I reboot my device : )

I'm using iOS 15.2

Posted by
Tomortec
Post not yet marked as solved Up vote reply of Tomortec Down vote reply of Tomortec

  • Surprisingly, this should be the accepted answer

    —
    apoorvet

  • Yes, It's work for me. My device iOS 15.3.1

    —
    PravinTadvi

  • Can't believe this answer isn't higher now.

    Must be some bizarre edge case with the app connecting to the backend. The fix even persists across deletions & reinstalls of my debug app for me!

    —
    Chrcarn
Add a Comment

Same for me, it disappears after I reboot my device. iOS 15.3.1

Posted by
spicheaubin@devolutions.net
Post not yet marked as solved Up vote reply of spicheaubin@devolutions.net Down vote reply of spicheaubin@devolutions.net
Add a Comment

So I was implementing a Background Notification and had the same problem where the "didReceiveRemoteNotification" delegate method was not getting called. Weirdly enough in my case, adding "badge": 0 worked. My sample payload looks like this:

{"aps":{"content-available":1,"apns-priority":5,"apns-push-type":"background","badge":0},"yourCustomKey":"1"}
Posted by
emilyfung
Post not yet marked as solved Up vote reply of emilyfung Down vote reply of emilyfung

  • this solution answered my question of not handling background notifications. It works if you remove "apns-push-type" too

    —
    CanisRed
Add a Comment

Make sure you to include these headers:

apns-push-type: background
apns-priority: 5

and this in the payload/body:

{"aps":{"content-available":1}}
Posted by
apavlovicABR
Post not yet marked as solved Up vote reply of apavlovicABR Down vote reply of apavlovicABR
Add a Comment

There is another scenario that most of the replies are not identifying and the docs are not mentioning either.

In my case, I had my device configured with a special uncommon/unrelated setting.

Go to Settings -> General -> Background App Refresh

You are presented with 3 options:

  1. Off
  2. Wi-Fi
  3. Wi-Fi Cellular Data

!IMPORTANT! There are a viral videos on social network recommending setting this to "Off" or "Wi-Fi" in order to save battery life / data plan. Thats when I set this to "OFF", and didReceiveRemoteNotification was never being called in the background, but strangely enough it was called once I opened the app.

Even if you have it on "Wi-Fi / Cellular Data", if you don't have internet, it wont be called (duhh), but most important, I think the guides should recommend having this small detail covered in case there are users that fall in the "condition" of having this set to "Off" or "Wi-Fi" and being on Cellular network <- this is more common case.

The conditional for this can be retrieved at: UIApplication.shared.backgroundRefreshStatus

https://developer.apple.com/documentation/uikit/uiapplication/1622994-backgroundrefreshstatus

And the funny thing is that it will mess up your logic once the device is in low-power mode, because it will automatically change the status to "Off".

There is nowhere to find that this impacts notifications arriving when app is in background mode, so thats odd. Anyways, hope this helps -roberto

Posted by
WilliamX
Post not yet marked as solved Up vote reply of WilliamX Down vote reply of WilliamX
Add a Comment

Interesting investigation, checked all things - but facing same issue. following input:

  • iPhone 7+
  • iOS 15.5
  • push notification and background refresh is allowed from app
  • battery is 100% ( low-power mode not activated )
  • Background modes checked: background fetch, remote notification
  • Push capabilities added (Remote notification, Background processing, Background fetch)

postman requests successful - 200 in response, but not trigger didReceiveRemoteNotification: `{ "to": "{{fcmToken}}", "yourCustomKey":"1", "aps":{ "content-available":1, "apns-priority":5, "sound": "", "apns-push-type":"background", "badge":0} }

{ "to": "{{fcmToken}}", "yourCustomKey":true, "aps":{ "content-available":true, "apns-priority":5, "sound": "", "apns-push-type":"background", "badge":0} }

{ "to": "{{fcmToken}}", "yourCustomKey":true, "aps":{ "content-available":true, "apns-priority":5, "sound": "default", "apns-push-type":"background", "badge":0} } ` and even that doesn't trigger didReceiveRemoteNotification Listing 7-1 shows an example of a JSON payload for a background update notification.  developer.apple.com

{ "to": "{{fcmToken}}", "aps" : { "content-available" : 1 }, "acme1" : "bar", "acme2" : 42 } Nothing from requests above works.

Yes I did reload iPhone

Any suggestion?? Hot to t-shoot next?

Posted by
ButtonClicked
Up vote reply of ButtonClicked Down vote reply of ButtonClicked
Add a Comment