Using Twilio Voice side by side with WebRTC - iOS
Twilio's Programmable Voice SDK for iOS is based upon a fork of the Chromium WebRTC project (webrtc.org). This heritage usually presents an interesting challenge of class conflicts when using other WebRTC dependencies alongside Twilio in your iOS application. We have designed Voice SDK 3.x and above to work alongside other libraries that also inherit from webrtc. However, in the case you run into conflict issues, follow this guide for ways how to resolve conflicts.
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 Voice classes are prefixed with TVO.
Consider the following Podfile which consumes both Twilio Voice and WebRTC:
_10source 'https://github.com/CocoaPods/Specs'_10_10target 'TARGET_NAME' do_10 platform :ios, '10.0'_10 pod 'TwilioVoice', '4.0.0'_10 pod 'GoogleWebRTC'_10end
Some classes with the RTC prefix are present both in WebRTC (publicly) and in Twilio Voice (privately). When classes are loaded by the Objective-C runtime, any conflicts which occur are raised in your console logs: