Post

Replies

Boosts

Views

Activity

Notification Service Extension in iOS works sometimes but stops working other times. User needs to restart device to get it working again.
We have an app where the notification service extension works well most of the time. However, sometimes we have noticed that the extension completely stops working even when the notification is sent successfully via the APNS server in production. We do not see even the log from the didReceive() function in that case. The only way we can get the extension working again is after restarting the iPhone. Trying to understand when this might happen? Is it something that is throttled by iOS? Would it happen when the device memory is low or the app is using too much memory? We have seen the extension crash sometimes due to hitting memory limits, however, the extension process is spawned again when a new notification comes in. Any kind of help or guidance would be greatly appreciated. Thanks We have setup acknowledgment API calls in the notification service extension processing to be notified when the notifications reach the device. So based on that we know how often the devices stop responding with the ACK to sent notifications. It happens seldom with some users and we have to ask them to restart their device to get the extension functional again.
4
2
2.3k
Jul ’23
Started seeing this issue happen frequently with Call Directory extension from iOS 15 onwards: Domain=com.apple.CallKit.error.calldirectorymanager Code=2 "(null)".
Hi, We have an app that manages incoming and outgoing calls for users. As part of that, the app needs to frequently keep updating the list of blocked numbers in the Call Directory Extension. The functionality was working quite well till iOS 14, however, since we started testing on iOS 15, we're seeing a lot of these errors when we try to reload the Call Directory extension: Domain=com.apple.CallKit.error.calldirectorymanager Code=2 "(null)" The documentation says this error code means: The call directory manager was interrupted while loading the app extension. We're not sure why it was interrupted and was it interrupted by the OS or by something that we did from our app. Please let us know when this error code might happen and if there's anything we can do from the app side to fix it.
1
1
761
Nov ’21