How to ensure a CallKit Call is connected before Call is answered?

Question

I have a VOIP App with Sinch Video integration. If the App is running from the background there is a window of about 1 - 3 seconds where the VOIP Push gets send through but the Sinch Call is not yet connected. (iOS13 requirement of reporting VOIP Push immediately).

In Apple's documentation they give this Hint:

Responding to VoIP Notifications from PushKit

If the recipient of a call answers before the app establishes a connection to your server, don't fulfill the CXAnswerCallAction object sent to the provider:performAnswerCallAction: method of your delegate immediately. Instead, wait until you establish a connection and then fulfill the object. While it waits for your app to fulfill the request, the incoming call interface lets the user know that the call is connecting, but not yet ready.

This behavior can be observed by Facetime as well, were often for a short period of time CallKit shows connecting...

I can not by the life of it figure out how to properly follow this advice by Apples documentation.

Is there any way I can per standard let the AnswerCallAction always delay the answering process by let's say 2 seconds?

here is my relevant provider delegate method:

func provider(_ provider: CXProvider, perform action: CXAnswerCallAction) {
    if (!(CommunicationService.shared?.tellGuardAnswerCallAction())!){
        action.fail()
        print("CXCallDelegate CXProvider: ERROR Answering Call")
        return
    }
    self.callManager.removeAll()
    CommunicationService.shared?.cDotAnswer()
    action.fulfill()        
}

If I answer the call before the Sinch Call and the UIKit Call are connected then the Call will not work. So ideally I would always give the code about 1 - 2 seconds time to connect OR check if the Sinch Call is connected before proceeding to action.fulfill()

Adeyemi Seun · Answer 1 · 2021-03-02T19:39:17.707

In my own case if the phone is locked and I didn't call action.fulfill() within 2secs it abruptly ends call the call.

Finally after several days the final solution was to use DispatchGroup. The DispatchGroup will make CallKit to wait to be fulfilled. You can read more about dispatch group.

   let myGroup = DispatchGroup()
   myGroup.enter()
   let info = getInfoFromTheWeb()
   //When you get info from simple call
   myGroup.leave()
  //When your call leave() function following code will be execute
  myGroup.notify(queue: DispatchQueue.main) {
         action.fulfill
        }

score 0 · Answer 2 · answered Sep 09 '20 at 14:21

I have faced the same issue. This issue occurs only when the App is in background and the device is in Locked State.

The fix is easy. Once the New Incoming Call is reported by Call Kit, You need to fullfill the answer action in performAnswerCallAction method.

- (void)provider:(CXProvider *)provider performAnswerCallAction:(CXAnswerCallAction *)action {

 UIApplicationState applicationState = [[UIApplication
 sharedApplication] applicationState];
 
 if(applicationState == 2){
 
         double delayInSeconds = 3.0;
         dispatch_time_t popTime = dispatch_time(DISPATCH_TIME_NOW, (int64_t)(delayInSeconds * NSEC_PER_SEC));
         dispatch_after(popTime, dispatch_get_main_queue(), ^(void){
             NSLog(@"provider:performAnswerCallAction Fullfilled in Application Background State : %@", uuid);
             [action fulfill];
         });
     }else{
         NSLog(@"provider:performAnswerCallAction Fullfilled in Application Foreground State : %@", uuid);
         [action fulfill];
 }

}

}

Apple suggests us to wait till the connection gets established before fulfilling the PerformAnswerAction.

How to ensure a CallKit Call is connected before Call is answered?

2 Answers2