Thanks for the detailed explanation. I have a follow-up question about this: Is the ~24-hour reset behavior different when using reportNewIncomingVoIPPushPayload from a Notification Service Extension? My app encountered the same issue after it failed to register PKPushRegistry in time. While the app was restricted, notifications continued reaching the extension, which called reportNewIncomingVoIPPushPayload, but no call screen was presented. callservicesd logged: Application <private> will not be launched because it failed to report an incoming call too many times (or repeatedly crashed.) VoIP push for app <private> dropped on the floor This continued for about 30 hours. I then stopped placing calls to the device for 24 hours, and calls started working again afterward. When reportNewIncomingVoIPPushPayload is called but the resulting call is dropped and no call screen is presented, does that count as another failure and restart the ~24-hour restriction period?