Today we announce the CallKit support in QuickBlox iOS WebRTC SDK!
CallKit lets you integrate your calling services (from your app) with other call-related apps on the system. For incoming and outgoing calls, CallKit displays the same interfaces as the Phone app, giving your app a more native look and feel.
Now you are able to integrate the CallKit API in your apps and to help you we prepared a code sample:
Video chat sample + CallKit: https://github.com/QuickBlox/quickblox-ios-sdk/tree/master/sample-videochat-webrtc
CallKit Documentation: https://quickblox.com/developers/Sample-webrtc-ios#Apple_CallKit
iOS WebRTC SDK changelog
- Fixed possible memory leak in some cases when using audio-only calls.
- Now corresponds to QBRTCAudioSessionActivationDelegate protocol. Use it to notify QBRTCAudioSession class that AVAudioSession was activated outside of rtc class itself. The most recent example is CallKit. Check this guide for more information.
- Added useManualAudio property and changed audioEnabled property default value to NO (both properties have NO as default value). If you set useManualAudio to YES, WebRTC will not initialize the audio unit automatically when an audio track is ready for playout or recording. Instead, applications should call setAudioEnabled. If NO, WebRTC will initialize the audio unit as soon as an audio track is ready for playout or recording. The most recent example is usage in CallKit, where we need to wait for AVAudioSession to be activated by Apple first, and then initialize audio manually. Check this guide for more information. If useManualAudio is NO, then audioEnabled property value does not affect anything.
- Fixed issue where video gravity was incorrect when the class was initialized while an app is in the background.
New SDK is available on QuickBlox website and CocoaPods