7.0 Changelog: Twilio Video Android
The Twilio Programmable Video SDKs use Semantic Versioning. Twilio supports version N-1 for 12 months after the first GA release of version N. We recommend you upgrade to the latest version as soon as possible to avoid any breaking changes.
Support for 6.x will cease on September 17th, 2022. This branch will only receive fixes for critical issues until that date. Check this guide when planning your migration to 7.x.
Support for 5.x will cease on December 4th, 2021. This branch will only receive fixes for critical issues until that date. Check this guide when planning your migration to 6.x.
Versions 4.x and below reached End of Life on September 8th, 2021. See the changelog here.
7.0.3 (December 6th, 2021)
- Programmable Video Android SDK 7.0.3 [Maven Central], [docs]
- Programmable Video Android KTX SDK 7.0.3 [Maven Central], [docs]
API Changes
- Added error code definition
PARTICIPANT_SESSION_LENGTH_EXCEEDED_EXCEPTION.
Bug Fixes
- Fixed a bug where if an exception occurs when connecting to a Room, the Room instance could leak and setting a custom audio device could fail.
- Fixed a bug where media could incorrectly be detected as not flowing after the network connectivity changes.
Known Issues
- As of 6.0.0 of the SDK, hardware video encoding doesn't publish all of the three simulcast layers when VP8 simulcast is enabled on Android. This affects Video Content Preferences from working properly for subscribing video participants since the feature requires all three simulcast layers to switch between. Our team is working on a fix for this, but the feature does work when VP8 simulcast is used to publish video from participants using the Javascript or iOS SDKs.
- Video Content Preferences might prefer larger video than needed when device orientations are mismatched. For example, if a participant in landscape mode publishes video, then the subscribing participant must also be in landscape mode in order for the correctly sized simulcast layers to be selected. The same is true for the portrait orientation.
- When the publisher is publishing video at 720p with VP8 simulcast enabled and the subscriber varies their hints between 180p, 360p, and 720p, sometimes the subscriber receives larger video than expected.
Size Report
| ABI | APK Size Impact |
|---|---|
| x86 | 5.8MB |
| x86_64 | 5.8MB |
| armeabi-v7a | 4.3MB |
| arm64-v8a | 5.5MB |
| universal | 20.7MB |
7.0.2 (November 3rd, 2021)
- Programmable Video Android SDK 7.0.2 [Maven Central], [docs]
- Programmable Video Android SDK KTX 7.0.2 [Maven Central], [docs]
New Features
- The SDK now supports audio only rooms and added two error codes, ROOM_AUDIO_ONLY_FLAG_NOT_SUPPORTED_EXCEPTION (53124) & TRACK_TRACK_KIND_NOT_SUPPORTED_EXCEPTION (53125).
Enhancements
- Improved reconnection time after network connectivity disruptions.
Known Issues
- As of 6.0.0 of the SDK, hardware video encoding doesn't publish all of the three simulcast layers when VP8 simulcast is enabled on Android. This affects Video Content Preferences from working properly for subscribing video participants since the feature requires all three simulcast layers to switch between. Our team is working on a fix for this, but the feature does work when VP8 simulcast is used to publish video from participants using the Javascript or iOS SDKs.
- Video Content Preferences might prefer larger video than needed when device orientations are mismatched. For example, if a participant in landscape mode publishes video, then the subscribing participant must also be in landscape mode in order for the correctly sized simulcast layers to be selected. The same is true for the portrait orientation.
- When the publisher is publishing video at 720p with VP8 simulcast enabled and the subscriber varies their hints between 180p, 360p, and 720p, sometimes the subscriber receives larger video than expected.
Size Report
| ABI | APK Size Impact |
|---|---|
| x86 | 5.8MB |
| x86_64 | 5.8MB |
| armeabi-v7a | 4.3MB |
| arm64-v8a | 5.5MB |
| universal | 20.7MB |
7.0.1 (October 15th, 2021)
- Programmable Video Android SDK 7.0.1 [Maven Central], [docs]
- Programmable Video Android SDK KTX 7.0.1 [Maven Central], [docs]
Bug Fixes
- Fixed an interoperability bug between JavaScript, iOS and Android SDKs which could cause subscription events not to fire in a Peer-to-Peer or Go Room. [VIDEO-7334] #211
Known Issues
- As of 6.0.0 of the SDK, hardware video encoding doesn't publish all of the three simulcast layers when VP8 simulcast is enabled on Android. This affects Video Content Preferences from working properly for subscribing video participants since the feature requires all three simulcast layers to switch between. Our team is working on a fix for this, but the feature does work when VP8 simulcast is used to publish video from participants using the Javascript or iOS SDKs.
- Video Content Preferences might prefer larger video than needed when device orientations are mismatched. For example, if a participant in landscape mode publishes video, then the subscribing participant must also be in landscape mode in order for the correctly sized simulcast layers to be selected. The same is true for the portrait orientation.
- When the publisher is publishing video at 720p with VP8 simulcast enabled and the subscriber varies their hints between 180p, 360p, and 720p, sometimes the subscriber receives larger video than expected.
Size Report
| ABI | APK Size Impact |
|---|---|
| x86 | 5.8MB |
| x86_64 | 5.7MB |
| armeabi-v7a | 4.3MB |
| arm64-v8a | 5.4MB |
| universal | 20.6MB |
7.0.0 (September 16th, 2021)
- Programmable Video Android SDK 7.0.0 [Maven Central], [docs]
- Programmable Video Android SDK KTX 7.0.0 [Maven Central], [docs]
New Features
- The SDK has been upgraded to use Chromium WebRTC 88.
- The SDK uses Unified Plan SDP semantics instead of Plan-B. This brings several important benefits:
- Improved interoperability with Firefox, Safari and Chrome in Peer-to-Peer and Go Rooms.
- Track level operations like publishing and unpublishing are more reliable.
- Improved performance of
Room.getStats()by adopting the W3C standardized RTC stats API. - Unused codecs for a track are removed from the local SDP offer in order to reduce the SDP size, once codecs for the track have been negotiated.
API Changes
- The minimum Android SDK version has been increased from 16 to 21. Please visit our migration guide for more details on how to update your application to 7.0!
- The ordering of
RemoteParticipantObserver.onAudioTrackSubscribed()andRemoteParticipantObserver.onVideoTrackSubscribed()is not strictly guaranteed. In this release the ordering of these callbacks may be different when compared to previous releases. - The value of
LocalVideoTrackStats.frames_encodednow reflects the total number of frames encoded for a simulcast track.
Bug Fixes
- Fixed a bug causing the Connect Option
enableIceGatheringOnAnyAddressPortsnot to have any effect.
Known Issues
- As of 6.0.0 of the SDK, hardware video encoding doesn't publish all of the three simulcast layers when VP8 simulcast is enabled on Android. This affects Video Content Preferences from working properly for subscribing video participants since the feature requires all three simulcast layers to switch between. Our team is working on a fix for this, but the feature does work when VP8 simulcast is used to publish video from participants using the Javascript or iOS SDKs.
- Video Content Preferences might prefer larger video than needed when device orientations are mismatched. For example, if a participant in landscape mode publishes video, then the subscribing participant must also be in landscape mode in order for the correctly sized simulcast layers to be selected. The same is true for the portrait orientation.
- When the publisher is publishing video at 720p with VP8 simulcast enabled and the subscriber varies their hints between 180p, 360p, and 720p, sometimes the subscriber receives larger video than expected.
Size Report
| ABI | APK Size Impact |
|---|---|
| x86 | 5.8MB |
| x86_64 | 5.7MB |
| armeabi-v7a | 4.3MB |
| arm64-v8a | 5.4MB |
| universal | 20.6MB |
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 by visiting Twilio's Community Forums or browsing the Twilio tag on Stack Overflow.