Judging by this subforum, others are experiencing this same issue lately, namely that application(_:didReceiveRemoteNotification:fetchCompletionHandler:) isn't being called, which seems to indicate that silent notifications are just not coming in anymore.
For us, this seems to have started around the time iOS13 was released, possibly a little earlier, but we've only just noticed recently and started troubleshooting it.
- We use AWS SNS to dispatch both active and silent notifications
- The active notifications are all working just fine
- AWS SNS logs indicate that the silent notifications are correctly sent to APNS (status 200)
- Yet our app either never receives them or never calls the didReceiveRemoteNotification method in AppDelegate
Solutions we've tried:
- Ensuring that the notification payload doesn't have any of the user-visible properties (alert dictionary)
- Setting the new apns-push-type APNS header, along with setting the priority header to 5
- Omitting the apns-push-type header and priority
Nothing seems to make a difference, and the silent notifications are simply never delivered. We've been testing this across multiple devices with different usage activity patterns for weeks now, and not a single silent notification has ever come through.
Does anyone have any insight on recent APNS changes or Notification API changes that may be causing this issue?
Or alternatively, any idea how to debug this further, given that APNS itself is a black box? As in, the furthest we can see from our backend is the successful delivery of the notification request to APNS, and the only thing we can see from our client's side is that the didReceiveRemoteNotification method is never being called. Are there any other troubleshooting approaches?