Skip to contentSkip to navigationSkip to topbar
Rate this Page:

Using Twilio Video side by side with WebRTC - iOS 3.x


(warning)

Warning

This page is for reference only. We are no longer onboarding new customers to Programmable Video. Existing customers can continue to use the product until December 5, 2024(link takes you to an external page).
We recommend migrating your application to the API provided by our preferred video partner, Zoom. We've prepared this migration guide(link takes you to an external page) to assist you in minimizing any service disruption.

Twilio's Programmable Video SDK for iOS is based upon a fork of the Chromium WebRTC project (webrtc.org(link takes you to an external page)). This heritage presents an interesting challenge when using other WebRTC dependencies alongside Twilio in your iOS application.

If you use the WebRTC Objective-C APIs or another Chromium WebRTC based SDK, please read on to learn how you can eliminate class conflicts with Twilio Video.

How do conflicts occur?

Objective-C does not support the concept of namespaces. Instead, developers typically use a 3-4 letter prefix to uniquely identify their classes. WebRTC classes are prefixed with RTC, while Twilio Video classes are prefixed with TVI.

Consider the following Podfile which consumes both Twilio Video and WebRTC.


_10
source 'https://github.com/CocoaPods/Specs'
_10
_10
target 'TARGET_NAME' do
_10
platform :ios, '9.0'
_10
pod 'TwilioVideo', '2.2.2'
_10
pod 'GoogleWebRTC'
_10
end

Some classes with the RTC prefix are present both in WebRTC (publicly) and in Twilio Video (privately). When classes are loaded by the Objective-C runtime, any conflicts which occur are raised in your console logs:

You can see that classes like RTCAudioSession are provided by both libraries. When classes conflict at runtime, the version which is loaded is undefined. This could result in unexpected behavior or crashes in your application.

How do I resolve class conflicts?

One technique used to resolve class conflicts is to rename (prefix) the impacted classes. As of version 2.3.0, Twilio Video now prefixes RTC classes with TVI. For example, RTCAudioSession now becomes TVIRTCAudioSession.

If you wish to use Twilio Video side by side with other WebRTC dependencies we recommend that you update to 2.3.0 or newer to eliminate class conflicts.


Rate this Page: