Changelog: Twilio Video iOS Latest

The Twilio Programmable Video SDKs use Semantic Versioning.

4.3.0 (February 3, 2021)

API の変更点

• Added new error code, CameraSource.Error.cameraPermissionDenied

バグ修正

• CameraSouce.startCapture() now properly raises the CameraSource.Error.cameraPermissionDenied error when attempting to start capturing the camera when a user has declined the camera permissions.

既知の問題

• The TwilioVideo.xcframework does not currently support the simulator on Apple Silicon arm64 Macs.
• Carthage is not currently a supported distribution mechanism for Twilio Video. Carthage does not currently work with .xcframeworks as documented here. Once Carthage supports binary .xcframeworks, Carthage distribution will be re-added.
• Unpublishing and republishing a LocalAudioTrack or LocalVideoTrack might not be seen by Participants. #34
• H.264 video might become corrupted after a network handoff. #147
• iOS devices do not support more than three H.264 encoders. Refer to #17 for suggested work arounds.
• 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]

4.2.0 (January 27, 2021)

改善点

• The minimum iOS version supported at build time has been lowered from 11.0 to 9.0. Though the Twilio Video APIs are only available on iOS 11.0 and above, you can still build iOS 9.x and 10.x apps with the Video SDK.

API の変更点

• Calling VideoTrack.addRenderer() multiple times with the same VideoRenderer now throws a helpful NSInvalidArgumentException instead of firing NSAssert.

既知の問題

• The TwilioVideo.xcframework does not currently support the simulator on Apple Silicon arm64 Macs.
• Carthage is not currently a supported distribution mechanism for Twilio Video. Carthage does not currently work with .xcframeworks as documented here. Once Carthage supports binary .xcframeworks, Carthage distribution will be re-added.
• Unpublishing and republishing a LocalAudioTrack or LocalVideoTrack might not be seen by Participants. #34
• H.264 video might become corrupted after a network handoff. #147
• iOS devices do not support more than three H.264 encoders. Refer to #17 for suggested work arounds.
• 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]

Size Impact

4.1.0 (January 13, 2021)

改善点

• The minimum supported iOS version has been lowered from 12.0 to 11.0. On iOS 11.x simulators, video rendering with VideoView is not supported.

バグ修正

• Fixed a bug where the VideoView was not applying the native scale factor to the drawable size. This was a regression introduced in version 4.0.1.#159

既知の問題

• The TwilioVideo.xcframework does not currently support the simulator on Apple Silicon arm64 Macs.
• Carthage is not currently a supported distribution mechanism for Twilio Video. Carthage does not currently work with .xcframeworks as documented here. Once Carthage supports binary .xcframeworks, Carthage distribution will be re-added.
• Unpublishing and republishing a LocalAudioTrack or LocalVideoTrack might not be seen by Participants. #34
• H.264 video might become corrupted after a network handoff. #147
• iOS devices do not support more than three H.264 encoders. Refer to #17 for suggested work arounds.
• 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]

Size Impact

4.0.1 (December 18, 2020)

バグ修正

• Fixed a bug where the video renderer was setting the drawable size incorrectly. This was causing pixelated video when rendered on an external display using the Screen Mirroring.#123
• Fixed a bug where publishing multiple Tracks with the same name may result in a crash if network quality is enabled.

Distribution Changes

• Removed the Poco section from Acknowledgements.md since Poco is no longer a dependency

既知の問題

• VideoView may display pixelated video. #159
• The TwilioVideo.xcframework does not currently support the simulator on Apple Silicon arm64 Macs.
• Carthage is not currently a supported distribution mechanism for Twilio Video. Carthage does not currently work with .xcframeworks as documented here. Once Carthage supports binary .xcframeworks, Carthage distribution will be re-added.
• Unpublishing and republishing a TVILocalAudioTrack or TVILocalVideoTrack might not be seen by Participants. #34
• H.264 video might become corrupted after a network handoff. #147
• iOS devices do not support more than three H.264 encoders. Refer to #17 for suggested work arounds.
• 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]

Size Impact

4.0.0 (December 4, 2020)

改善点

• The iOS SDK is based on WebRTC-83.
• The iOS SDK is built with Xcode 12.0.
• Twilio Video is now delivered as an .xcframework. The .xcframework package includes the .dSYM and .bcsymbolmap files to allow developers to symbolicate crash reports.
• Twilio Video is now distributed as a Swift Package.
• Enabled Metal rendering on the iOS simulator.
• You can now share video of your app's screen to a Room using AppScreenSource. The Video SDK uses ReplayKit internally for in-app screen capture. AppScreenSource conforms to VideoSource and uses RPScreenRecorder to capture video of your app's screen. Here is a brief example:

if let source = AppScreenSource(), let track = LocalVideoTrack(source: source) {
    room.localParticipant?.publishVideoTrack(track)
    source.startCapture()
}

• Discontinuous transmission (DTX) is enabled by default for the Opus codec. Disabling DTX will result in higher bitrate for silent audio while using the Opus codec. The TVIOpusCodec class now has a new initializer [TVIOpusCodec initWithDtxEnabled:] and a property dtxEnabled.
• Added the TVIParticipantState enumeration.
• Added the TVIParticipant.state property.
• Added new delegate methods [TVIRoomDelegate room:participantIsReconnecting:] and [TVIRoomDelegte room:participantDidReconnect:] to TVIRoomDelegate. These callbacks will be raised when a TVIRemoteParticipant is attempting to reconnect to a room due to a signaling network interruption. NOTE: It can take up to 15 seconds for our signaling backend to detect that a RemoteParticipant's connection has been disrupted due to a network degradation or handoff.
• isRecording property in TVIRoom now accurately reflects the current recording state of the TVIRoom. In the previous versions of the SDK, isRecording could return false positives. In TVIRoomDelegate the roomDidStartRecording and roomDidStopRecording callbacks will now be invoked when recording for at least a single track in the TVIRoom has begun and ended respectively.

API Updates

• Added AppScreenSource to control video capture of your app's screen.
• Removed the TVIRemoteParticipant.connected property in favor of TVIParticipant.state.

Removed the following deprecated APIs

• Removed the deprecated OpenGL Video Renderer APIs:
  • VideoView.RenderingType
  • [VideoView initWithFrame:delegate:renderingType:renderingType]
• Removed the deprecated abortOnIceServersTimeout and iceServersTimeout properties from IceOptions and IceOptionsBuilder.

Distribution Changes

• Twilio Video iOS SDK is no longer being shipped as a static library.
• Twilio Video no longer depends on the Poco C++ Libraries.

既知の問題

• The TwilioVideo.xcframework does not currently support the simulator on Apple Silicon arm64 Macs.
• Carthage is not currently a supported distribution mechanism for Twilio Video. Carthage does not currently work with .xcframeworks as documented here. Once Carthage supports binary .xcframeworks, Carthage distribution will be re-added.
• Unpublishing and republishing a TVILocalAudioTrack or TVILocalVideoTrack might not be seen by Participants. #34
• H.264 video might become corrupted after a network handoff. #147
• iOS devices do not support more than three H.264 encoders. Refer to #17 for suggested work arounds.
• 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]
• Publishing multiple tracks with the same name may result in a crash if network quality is enabled. To avoid this, use unique names for each track in the TVIRoom.

Size Impact