Menu

Expand
Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Changelog: Twilio Video iOS

The Twilio Programmable Video SDKs use Semantic Versioning.

3.0.0-beta3 (August 5, 2019)

Enhancements

  • The Participant's signaling connection now conforms to Twilio's TLS & Cipher Suite Security Policy. Support for TLS versions older than 1.2 has been removed. [CSDK-3020]
  • Adjusted the buffer sizes used for signaling messages to reduce network fragmentation. [CSDK-2920]
  • Setting TVILogModuleSignaling enables logging of low level connection events at TVILogLevelTrace. [ISDK-2446]

Bug Fixes

  • WebSocket errors are handled immediately, rather than waiting for a timeout to occur. [CSDK-3025]
  • Handle rare exceptions when constructing a WebSocket. [CSDK-2755]

Known Issues

  • Future 3.0.0-beta releases will reduce the number of round-trips required to connect to a Room. [CSDK-2902]
  • In rare cases, the SDK might timeout during a TCP handshake and should be more aggressive at establishing a connection. [CSDK-2942]
  • Server side deflate compression is disabled due to occasional errors when reading messages. [CSDK-2949]
  • Unpublishing and republishing a TVILocalAudioTrack or TVILocalVideoTrack might not be seen by Participants. #34
  • Typically, a maximum of three H.264 encoders can be used at once. When this limit is exceeded no errors are raised and new video Tracks are not encoded. #17
  • Publishing H.264 video at greater than 1280x720 @ 30fps is not supported. If a failure occurs then no error is raised to the developer. [ISDK-1590]

3.0.0-beta2 (July 16, 2019)

API Changes

  • Renamed + [TwilioVideoSDK version] to + [TwilioVideoSDK sdkVersion] to alleviate the clash with NSObject's version method.
  • Removed the type argument label for the Swift definition of [TVICameraSource captureDeviceForPosition:type]. In Swift, the function is now declared as class func captureDevice(position: AVCaptureDevice.Position, deviceType: AVCaptureDevice.DeviceType) -> AVCaptureDevice?.
  • Updated the Swift audio sample rate constant names to remove the redundant Audio. For instance AudioFormat.AudioSampleRate8000 is now AudioFormat.SampleRate8000.
  • Updated the Swift audio format channels constant names to remove the redundant Audio. For instance AudioFormat.AudioChannelsMono is now AudioFormat.ChannelsMono.
  • Refactored the TVILocalParticipantDelegate and TVIRemoteParticipantDelegate methods to follow the did naming convention for consistency with the other delegate methods. See the Migrating from 2.x to 3.x guide for more information.

Bug Fixes

  • The SDK will consistently recover the Participant's connection after multiple failed network handovers, or multiple failures on a single network. [CSDK-2957, CSDK-3007]
  • Failures in the Participant's connection are always detected within 15 seconds. [CSDK-2927]
  • Improved DNS retry logic and error handling. [CSDK-2801]
  • Disabled server side deflate compression due to occasional errors when reading messages. [CSDK-3004]
  • Security improvements. [CSDK-2986, CSDK-3005]

Known Issues

  • Future 3.0.0-beta releases will reduce the number of round-trips required to connect to a Room. [CSDK-2902]
  • Setting TVILogModuleSignaling does not produce any logging. [ISDK-2446]
  • In rare cases, the SDK might timeout during a TCP handshake and should be more aggressive at establishing a connection. [CSDK-2942]
  • Server side deflate compression is disabled due to occasional errors when reading messages. [CSDK-2949]
  • Unpublishing and republishing a TVILocalAudioTrack or TVILocalVideoTrack might not be seen by Participants. #34
  • Typically, a maximum of three H.264 encoders can be used at once. When this limit is exceeded no errors are raised and new video Tracks are not encoded. #17
  • Publishing H.264 video at greater than 1280x720 @ 30fps is not supported. If a failure occurs then no error is raised to the developer. [ISDK-1590]

3.0.0-beta1 (June 6, 2019)

The 3.0 release removes support for iOS 9.0, and raises the minimum supported iOS version to 10.0. Twilio Video 2.x releases will continue to support iOS 9.0 and later.

Enhancements

  • The SDK uses a new WebSocket based signaling transport, and communicates with globally available signaling Servers over IPv4 and IPv6 networks.
  • Added the TVIConnectOptions.region property. By default, the Client will connect to the nearest signaling Server determined by latency based routing. Setting a value other than "gll" bypasses routing and guarantees that signaling traffic will be terminated in the region that you prefer.
let connectOptions = ConnectOptions(token: accessToken) { (builder) in
    builder.region = "us1"
    builder.roomName = "my-room"
}
self.room = TwilioVideoSDK.connect(with: connectOptions, delegate: self)
  • Participants are considered to be reconnecting within 15 seconds, and are disconnected from a Room after 45 seconds of lost connectivity. #99

API Changes

  • Twilio Video has been updated for better Swift interoperability. See the Migrating from 2.x to 3.x guide for more information.
    • The TwilioVideo Obj-C class has been renamed to TwilioVideoSDK to reduce possible namespace issues in Swift due to the Module containing a Type with the same name.
    • The TVI prefix has been removed from all Twilio Video types
    • Many of the delegate function declarations have been revamped for better clarity of their intent
    • Some of the class method declarations have been revamped for better clarity of their intent
  • The TVIAudioSessionActivated() and TVIAudioSessionDeactivated() methods have been removed as the Video SDK no longer needs to terminate the signaling connection when an app is backgrounded.
  • Removed the deprecated TVIVideoCapturer APIs:
    • TVIVideoCapturer
    • TVICameraCapturer
    • TVIScreenCapturer
    • TVIVideoConstraints
    • TVILocalVideoTrack.capturer
    • TVILocalVideoTrack.constraints
    • TVILocalVideoTrack.trackWithCapturer:
    • TVILocalVideoTrack.trackWithCapturer:enabled:constraints:name:
  • Removed TVIAudioOptions that are no longer supported by WebRTC:
    • TVIAudioOptions.levelControl
    • TVIAudioOptions.levelControlInitialPeakLevelDBFS
    • TVIAudioOptionsBuilder.levelControl
    • TVIAudioOptionsBuilder.levelControlInitialPeakLevelDBFS
  • Removed the TVIVideoRenderer.optionalPixelFormats property due to lack of use. A TVIVideoRenderer is expected to support any valid TVIPixelFormat or drop incoming frames if it can't process them.

Bug Fixes

  • Participants can send and receive messages that are larger than 16 KB.
  • Renamed kDefaultAVAudioSessionConfigurationBlock to kTVIDefaultAVAudioSessionConfigurationBlock so that TwilioVoice.framework and TwilioVideo.framework may be used in the same application.
  • Fixed a crash that could occur when using a TVIVideoSource, and the source's buffer pool becomes empty.

Known Issues

  • Future 3.0.0-beta releases will reduce the number of round-trips required to connect to a Room. [CSDK-2902]
  • If heartbeats are not received, the signaling connection may take up to 45 seconds to be disconnected instead of 15 seconds. [CSDK-2927]
  • The SDK may crash if Network Quality or Dominant Speaker is enabled, and connectivity to the Room is lost, and the Room is deleted from within [TVORoomDelegate didDisconnectWithError:]. [CSDK-2950]
  • Setting TVILogModuleSignaling does not produce any logging. [ISDK-2446]
  • In rare cases, the SDK might timeout during a TCP handshake and should be more aggressive at establishing a connection. [CSDK-2942]
  • The WebSocket might close with a partial_deflate_block (code 5) error. [CSDK-2949]
  • Unpublishing and republishing a TVILocalAudioTrack or TVILocalVideoTrack might not be seen by Participants. #34
  • Typically, a maximum of three H.264 encoders can be used at once. When this limit is exceeded no errors are raised and new video Tracks are not encoded. #17
  • Publishing H.264 video at greater than 1280x720 @ 30fps is not supported. If a failure occurs then no error is raised to the developer. #388 [ISDK-1590]
Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.