Skip to main content

CallKit integration


CallKit allows us to have system-level phone integration. With that, we can use CallKit to present native incoming call screens, even when the app is closed. CallKit integration also enables the calls made through third-party apps be displayed in the phone's recent call list in the Phone app.

The StreamVideo SDK is compatible with CallKit, enabling a complete calling experience for your users.


In order to get started, you would need have a paid Apple developer account, and an app id with push notifications enabled.

In the "Signing & Capabilities" section of your target, make sure that in the "Background Modes" section you have selected:

  • "Voice over IP"
  • "Remote notifications"
  • "Background processing"

Screenshot shows the required background modes in Xcode

Next, you need to create a VoIP calling certificate. In order to do that, go to your Apple developer account, select "Certificates, Identifiers & Profiles" and create a new certificate. Make sure to select "Apple Push Notification service SSL (Sandbox & Production)", located under the "Services" section. Follow the steps to create the required certificate.

Screenshot shows the creation of a VoIP certificate

After you've created the certificate, you would need to convert the aps.cer file to a .p12 certificate file using keychain access and upload it to our dashboard.


Make sure that you configure no password for the p12 file.

Dashboard Configuration

In order to configure VoIP Push Notifications, you need to visit your app's dashboard. From there, select the Push Notifications menu option as you can see in the image below:

Screenshot shows the creation of a VoIP certificate

From there you can create a new configuration by clicking the New Configuration button. After selecting the Push Notification Provider you want, you will be asked to provide the following information:

Field NameUsage description
NameUsed to select this configuration in SDK or API calls.
DescriptionAllows you to set a description on the configuration to help identify its usage in your app's context.
Bundle/Topic IDYour app's bundle id to which the notification will be pushed to.
TeamIDThe Team ID is generated by Apple for your developer account. Can be found in the top right of your Apple developer account.
KeyIDThis is the unique identifier for the p8 authentication key. You can find your Key ID in the keys section of your Apple developer account.
.p8 Token or .p12 CertificateThe token or certificate that will be used to send the push notification.

For our example, we are using voip as name and we are filling the remaining information as you can see in the image below:

Screenshot shows the creation of a VoIP certificate

iOS app integration

From iOS app perspective, there are two Apple frameworks that we need to integrate in order to have a working CallKit integration: CallKit and PushKit. PushKit is needed for handling VoIP push notifications, which are different than regular push notifications.

We have a working CallKit integration in our demo app. Feel free to reference it for more details, while we will cover the most important bits here.

In order for the CallKit integration to work, you should have a logged in user into your app. For simplicity, we are saving the user in the UserDefaults, but we strongly discourage that in production apps, since it's not secure.

PushKit integration

For handling VoIP push notifications, we will create a new class, called VoIPPushService, that implements the PKPushRegistryDelegate. Internally, we will create an instance of PKPushRegistry, which requests the delivery and handles the receipt of PushKit notifications.

class VoIPPushService: NSObject, PKPushRegistryDelegate {

@Injected(\.streamVideo) var streamVideo

private let queue: DispatchQueue
private let registry: PKPushRegistry
private let tokenHandler: VoIPTokenHandler

var onReceiveIncomingPush: VoIPPushHandler

init(voIPTokenHandler: VoIPTokenHandler, pushHandler: @escaping VoIPPushHandler) {
self.tokenHandler = voIPTokenHandler
self.queue = DispatchQueue(label: "io.getstream.voip")
self.registry = PKPushRegistry(queue: queue)
self.onReceiveIncomingPush = pushHandler

When the app is started, we need to register for VoIP push notifications, by adding the following method to the VoipPushService:

func registerForVoIPPushes() {
self.registry.delegate = self
self.registry.desiredPushTypes = [.voIP]

You should call this method after the user authenticates in your app.

Next, we need to implement the PKPushRegistryDelegate:

func pushRegistry(_ registry: PKPushRegistry, didUpdate credentials: PKPushCredentials, for type: PKPushType) {
let deviceToken = { String(format: "%02x", $0) }.joined()
log.debug("pushRegistry deviceToken = \(deviceToken)")
Task {
await {
AppState.shared.voIPPushToken = deviceToken

func pushRegistry(_ registry: PKPushRegistry, didInvalidatePushTokenFor type: PKPushType) {
if let savedToken = tokenHandler.currentVoIPPushToken() {
Task {
try await streamVideo.deleteDevice(id: savedToken) nil)

func pushRegistry(
_ registry: PKPushRegistry,
didReceiveIncomingPushWith payload: PKPushPayload,
for type: PKPushType,
completion: @escaping () -> Void
) {
self.onReceiveIncomingPush((payload, type, completion))

When the user sign out , we need to unregister from VoIP push notifications, by adding the following method to the VoipPushService:

func unregisterForVoIPPushes() {
self.registry.delegate = nil
self.registry.desiredPushTypes = []

You will need to call this method once the signout flow has been completed.

Saving the PN credentials

We're implementing three methods here. The pushRegistry(_ registry: PKPushRegistry, didUpdate credentials: PKPushCredentials, for type: PKPushType) method is called when new push notifications credentials are provided. You should use this method to save the device token to our backend. In our sample app, we are storing it in our AppState object. Whenever the StreamVideo SDK is initalized, we are saving the token to our backend, by calling the setVoipDevice method.

private func setVoipToken() {
if let voipPushToken, let streamVideo {
Task {
try await streamVideo.setVoipDevice(id: voipPushToken)

Also, you should save the token locally, in order to be able to delete it from the backend if the user logs out. For simplicity, we're storing it in a simple UserDefaults wrapper, but in a real-world app you should store it in a more secure place, such as the iOS Keychain.

Removing the PN credentials

The pushRegistry(_ registry: PKPushRegistry, didInvalidatePushTokenFor type: PKPushType) is called when the push token is invalidated. When this method is called, you should delete the value saved with the method deleteDevice in StreamVideo.

try await streamVideo.deleteDevice(id: savedToken)

Receiving a push notification

The method pushRegistry(_ registry: PKPushRegistry, didReceiveIncomingPushWith payload: PKPushPayload, for type: PKPushType, completion: @escaping () -> Void) is called whenever a VoIP push notification is received. We're just passing this information to another object, called CallService (more on that shortly), by calling the onReceiveIncomingPush closure.

CallKit integration

The CallService class handles the onReceiveIncomingPush callbacks invoked by the VoipPushService. Whenever the handler is called, the CallService uses another class, called CallKitService, that handles the CallKit integration.

final class CallService {

static let shared = CallService()

let callService = CallKitService()
lazy var voIPPushService = makeVoIPPushService()

private init() {}

func registerForIncomingCalls() {
#if targetEnvironment(simulator)"CallKit notifications not working on a simulator")

private func unregisterForIncomingCalls() {
#if targetEnvironment(simulator)"CallKit notifications not working on a simulator")

private func makeVoIPPushService() -> VoIPPushService {
let defaultCallText = "Unknown Caller"

return .init(voIPTokenHandler: AppState.shared.unsecureRepository) { [weak self] payload, type, completion in
guard let self = self else {

let streamDict = payload.dictionaryPayload["stream"] as? [String: Any]
let callCid = streamDict?["call_cid"] as? String ?? "unknown"
let createdByName = streamDict?["created_by_display_name"] as? String ?? defaultCallText
let createdById = streamDict?["created_by_id"] as? String ?? defaultCallText

callCid: callCid,
displayName: createdByName,
callerId: createdById
) { _ in

The CallKitService has a method called reportIncomingCall, which reports the call to the OS:

func reportIncomingCall(
callCid: String,
displayName: String,
callerId: String,
completion: @escaping (Error?) -> Void
) {
let configuration = CXProviderConfiguration()
configuration.supportsVideo = true
configuration.supportedHandleTypes = [.generic]
configuration.iconTemplateImageData = UIImage(named: "logo")?.pngData()
let provider = CXProvider(
configuration: configuration
provider.setDelegate(self, queue: nil)
let update = CXCallUpdate()
let idComponents = callCid.components(separatedBy: ":")
if idComponents.count >= 2 {
self.callId = idComponents[1]
self.callType = idComponents[0]
let callUUID = UUID()
callKitId = callUUID
update.localizedCallerName = displayName
update.remoteHandle = CXHandle(type: .generic, value: callerId)
update.hasVideo = true
Task {
await {
with: callUUID,
update: update,
completion: completion

The method also saves the callId and callType, and it generates a call UUID, which is required by CallKit for identifying calls.

Before we report the call to CallKit, we are also setting up the StreamVideo client (if it's not setup already). Also, we are subscribing to web socket events. This is needed to handle the case when the caller stops the call - in this case we should also end the native calling screen.

private func setupStreamVideoIfNeeded() {
guard let currentUser = UnsecureUserRepository.shared.loadCurrentUser() else {
if AppState.shared.streamVideo == nil {
let streamVideo = StreamVideo(
apiKey: Config.apiKey,
user: currentUser.userInfo,
token: currentUser.token,
videoConfig: VideoConfig(),
tokenProvider: { result in
AppState.shared.streamVideo = streamVideo

private func subscribeToCallEvents() {
Task {
for await videoEvent in streamVideo.subscribe() {
guard let event = CallEventsHandler().checkForCallEvents(from: videoEvent) else {

switch event {
case .ended(_):
log.debug("received call event")

The call can happen completely inside the native calling screen, or be transferred to the app. With the latter scenario, the SDKs calling view is presented. Important aspect with this case is syncing the actions performed from the in-app call view with the CallKit actions.

First, we need to accept the call both from CallKit, as well as initiate the call inside the SDK. This is done with the provider(_ provider: CXProvider, perform action: CXAnswerCallAction) method in the CXProviderDelegate.

func provider(_ provider: CXProvider, perform action: CXAnswerCallAction) {
if !callId.isEmpty {
Task {
await {
Task { = callType, callId: callId)
AppState.shared.activeCall = call
try await call?.join()
await {
} else {

We're also listening to CallNotification.callEnded notification, published from the StreamVideo SDK. This notification is sent whenever the user ends the call from the in-app view.

@objc func endCurrentCall() {
guard let callKitId = callKitId else { return }
let endCallAction = CXEndCallAction(call: callKitId)
let transaction = CXTransaction(action: endCallAction)
self.callKitId = nil

Similarly, when the user decides to end the call via the CallKit interface, we need to cleanup the session in the StreamVideo SDK.

func provider(_ provider: CXProvider, perform action: CXEndCallAction) {
callKitId = nil
call = nil
Task {
await {
AppState.shared.activeCall = nil

Starting a call from Recents

When a call is started via CallKit, it appears in the "Recents" section in the native iOS phone app. Usually, when you tap on a recents entry, you should be able to call the person again.

For this, we need to add a INStartCallIntent intent extension. To do this, go to your targets in Xcode and add a new "Intents Extension".

After the extension is created, go to its IntentHandler and add the following code:

import Intents

class IntentHandler: INExtension, INStartCallIntentHandling {
override func handler(for intent: INIntent) -> Any {
return self

func handle(intent: INStartCallIntent, completion: @escaping (INStartCallIntentResponse) -> Void) {
let userActivity = NSUserActivity(activityType: NSStringFromClass(INStartCallIntent.self))
let response = INStartCallIntentResponse(code: .continueInApp, userActivity: userActivity)


In the Info.plist file of the extension, add the INStartCallIntent value in IntentsSupported, under NSExtension -> NSExtensionAttributes.

With this setup, our app has the ability to react to INStartCallIntents. Next, let's handle these intents in our SwiftUI code.

In the CallView in our DemoApp, we are adding the following code:

var body: some View {
HomeView(viewModel: viewModel)
.modifier(CallModifier(viewModel: viewModel))
.onContinueUserActivity(NSStringFromClass(INStartCallIntent.self), perform: { userActivity in
let interaction = userActivity.interaction
if let callIntent = interaction?.intent as? INStartCallIntent {

let contact = callIntent.contacts?.first

guard let name = contact?.personHandle?.value else { return }
viewModel.startCall(callId: UUID().uuidString, type: .default, members: [.init(id: name)], ring: true)

The important part is the onContinueUserActivity, where we listen to INStartCallIntents. In the closure, we are extracting the first contact and take their name, which is the user id. We use that name to start a ringing call.

Additionally, if you have integration with the native contacts on iOS (Contacts framework), you can extract the full name, phone number etc, and use those to provide more details for the members. Alternatively, you can call our queryUsers method to get more user information that's available on the Stream backend.

If you are using UIKit, you should implement the method application(_ application: UIApplication, continue userActivity: NSUserActivity, restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) in your AppDelegate, and provide a similar handling as in the SwiftUI sample.

Did you find this page helpful?