iOS 13 Killing app because it never posted an incoming call to the system after receiving a PushKit VoIP callback

by

On this thread from apple forums, someone from apple staff explained this:

On iOS 13.0 and later, incoming Voice over IP calls must be reported
when they are received and before the didReceiceIncomingPush() method
finishes execution, using the CallKit framework, or the system will
terminate your app.

Repeatedly failing to report calls may prevent
your app from receiving any more incoming call notifications.

Basically, you can no longer use VoIP pushes for non VoIP messaging,
and will need to use regular push notifications for those.

This was
announced during the WWDC session “Advances in App Background
Execution” https://developer.apple.com/videos/play/wwdc2019/707/

I’ve been searching for answers on how to adapt an app for this change, and what I could gather is the following:

Voip Pushes

When your app receive this kind of push, it will need to report a new incoming call using CallKit. Therefore, this kind of push will be exclusive for calls that use CallKit.

It’s recommended that you set the notification’s apns-expiration to 0, so you won’t receive a push and be forced to present a call screen for a call that already expired.

Push Notifications

Regular push notifications are another option. If your server has all the information you need to write the notification text, you can send notifications that won’t even run your app in the background. If you need to modify the content of the notification before presenting it to the user, you can use a Notification Service app extension, and if you need your app to be woken up and execute something in background, you can send silent push notifications.

Notification Service App Extension

To use this, you must set your notification’s mutable-content to 1. This way, your extension will receive the notification before it is presented to the user, allowing you to change its content, with a 30 seconds time limit.

The cons are that your app will stay in the background, only your extension will be allowed to run. This might mean that you will need to share information and code between your app and the extension, either by using user defaults, keychain, or by sharing your entire database (which might not be a simple task if your app is not prepared for that).

Silent Push Notifications

To send silent push notifications, you must set your notification’s content-available to 1 and remove it’s alert, badge and sound. This notification will wake up your app in the background, and call your app delegate’s didReceiveRemoteNotification.

The downsides are quite annoying for this option:

  • You will only get 30 seconds to run.
  • These notifications must have a apns-priority of 5, which might cause them to be grouped and delivered in bursts, and even throttled or not delivered.
  • If the user force closes the app, it will completely ignore all silent notifications until the user opens the app again.

More Related Contents:

  1. SendEmptyPushNotification to gateway.push.apple.com no longer working
  2. didRegisterForRemoteNotificationsWithDeviceToken not called in ios8, but didRegister…Settings is
  3. didReceiveRemoteNotification not called, iOS 10
  4. This certificate has an invalid issuer Apple Push Services
  5. Is it possible to opt-out of dark mode on iOS 13?
  6. What is Silent Push Notification? When does the device receive it?
  7. iOS application: how to clear notifications?
  8. Detecting sheet was dismissed on iOS 13
  9. didReceiveRemoteNotification when in background
  10. Xcode 11 & iOS13, using UIKIT can’t change background colour of UIViewController
  11. Missing Push Notification Entitlement
  12. Opt out of UISceneDelegate/SwiftUI on iOS
  13. C# SIP Stack/Library [closed]
  14. Callback Method if user declines Push Notification Prompt?
  15. How to fix “no valid ‘aps-environment’ entitlement string found for application” in Xcode 4.3?
  16. Implement PushKit and test in development behavior
  17. didReceiveRemoteNotification not working in the background
  18. SwiftUI @Binding Initialize
  19. iOS 13.1 Crash in AVAudio Player
  20. How to change the colors of a segment in a UISegmentedControl in iOS 13?
  21. Silent push notifications only delivered if device is charging and/or app is foreground
  22. How to Maintain VOIP socket connection in background?
  23. How do I forward a Twilio number to a VoIP phone?
  24. How to detect device name in Safari on iOS 13 while it doesn’t show the correct user agent?
  25. iOS 13 UIBarButtonItem not clickable and overlapping UINavigationBars when using UISearchController
  26. Chaining animations in SwiftUI
  27. How to catch all iOS Push Notifications with different user actions including tap on app icon
  28. How do I send a HTTP/2 POST request in PHP
  29. VoIP RTP Streaming from/to server (in Java) to/from android
  30. Firebase FCM silent push notifications for iOS

Leave a Comment