Introduction
The Vonage Video API Client SDK 2.36 is now available. This release brings five meaningful updates: a new error added to end-to-end encryption APIs, expanded client observability with quality-restriction insights, built-in publish retry logic for the JavaScript SDK, iOS 27 compatibility, and a security update to the CA root certificates embedded in the WebRTC library bundled in the native SDKs.
The 2.36 release is available across JavaScript (Web), iOS, Android, Linux, and Windows. For a complete list of changes, see the full release notes.
New Error Added to End-to-End Encryption APIs
The new OT_ENCRYPTION_NOT_ENABLED error provides additional information in situations where end-to-end encryption was not enabled. The error is returned when an encryption secret is set in a session that was not created with end-to-end encryption enabled.
Previously, this resulted in a silent error that was not exposed to the developer.
Client Observability: Quality Restriction Insights
Version 2.36 brings additional visibility into why a participant’s video quality changes during a session, building on the network condition reporting introduced in previous releases. This update is available across all SDKs: JavaScript (Web), iOS, Android, Linux, and Windows.
Previously, the SDK didn't report why video quality had been limited in some scenarios. Now the SDK provides more details for both publisher and
Two new fields in the subscriber video statistics address this directly:
- SenderQualityRestriction - reports restrictions applied by the immediate sender (the Media Router in routed sessions, or the publisher in relayed sessions).
SenderQualityRestriction - reports restrictions applied by the immediate sender (the Media Router in routed sessions, or the publisher in relayed sessions).
- RemotePublisherQualityRestriction - reports restrictions applied by the originating publisher.
RemotePublisherQualityRestriction - reports restrictions applied by the originating publisher.
Both fields use the same set of restriction types: none, spatial, temporal, both, and unknown.
Changes in sender quality restrictions are also surfaced through the existing Subscriber.VideoQualityChanged event, so applications that already listen to that event will receive the new data without any integration changes.
Two new NetworkReason values have also been added:
- NetworkReason.NoSubscribers - indicates that the publisher’s bitrate is limited because there are no active
NetworkReason.NoSubscribers - indicates that the publisher’s bitrate is limited because there are no active
- NetworkReason.DownstreamConstraint - indicates that the publisher’s bitrate is constrained by downstream receiver conditions, typically when scalable video is disabled.
NetworkReason.DownstreamConstraint - indicates that the publisher’s bitrate is constrained by downstream receiver conditions, typically when scalable video is disabled.
Together, these additions give applications the information needed to surface quality issues to end users in real time. Developers can act during the call, not after it ends.
For full details, see the Client Observability guide.
Built-in Retry for Publishing in the JavaScript SDK
Version 2.36 introduces built-in retry support for session.publish in the JavaScript SDK. The SDK now automatically handles recoverable transient errors during publishing, reducing the amount of error-handling code applications need to maintain.
This is an opt-in feature. The default behavior of session.publish is completely unchanged; existing integrations will continue to work as before.
To enable built-in retry, pass the new publisher options when initializing:
The three new publisher options are:
Option
Type
Default
Description
maxPublishTimeout
Number (ms)
15000
Maximum time for the publish to succeed. The SDK retries on any recoverable error within this window. Non-recoverable errors are returned immediately; expiry returns a timeout error.
onRetry
Function(error)
Callback invoked on each retry. Receives the triggering error. Use this to show a “Retrying…” indicator. Informational only - retries cannot be cancelled from here.
fallbackOnPartialPermission
Boolean
false
When true, if the user grants only some devices (e.g. microphone but not camera), publishing continues with the permitted devices instead of failing. Also degrades gracefully if a device is revoked after publishing starts.
The timeout behaves differently depending on how it is set. An explicitly configured value (e.g., maxPublishTimeout: 20000) acts as a hard timeout: the SDK stops retrying once the timer expires, regardless of connection state. When left at the default of 15000 ms, it behaves as a soft timeout: if the socket disconnects, the timer pauses until the connection is restored, then resumes. This prevents the SDK from giving up during temporary connectivity loss.
Non-recoverable errors such as OT_NOT_CONNECTED and OT_PERMISSION_DENIED are never retried, ensuring that real failures are surfaced immediately. The SDK uses exponential backoff for retry intervals.
iOS 27 Compatibility
Version 2.36 ensures full iOS 27 compatibility across the entire SDK. No integration changes are required by developers building applications on iOS 27. We also backported these compatibility changes to SDK version 2.35.2 to ensure readiness for the latest iOS release.
Security Update: eMudhra Root Certificate Distrust
Version 2.36 updates the root certificates embedded in the WebRTC library used by the native SDKs. Certificates issued by the compromised eMudhra (emSign) intermediate certificate authorities are no longer trusted.
In October 2026, the private keys of eight eMudhra intermediate certificate authorities were found to be recoverable, a serious security incident affecting browsers, operating systems, and a wide range of software stacks across the Internet. Because these keys are weak, an attacker could create a forged certificate for any domain and use it to impersonate servers or intercept traffic. For full details on the incident, see Cloudflare’s disclosure.
The SDK uses the WebRTC library’s embedded root certificates to verify secure connections to TURN servers over TLS. This update ensures that the SDK no longer accepts certificates issued by the affected certificate authorities, restoring the integrity of those connections. No integration changes are required; upgrading to version 2.36 is sufficient.
Getting Started
To upgrade to version 2.36, install the JavaScript SDK using the following command:
For native SDKs, visit our documentation for platform-specific installation instructions.
Note: The React Native SDK follows each native SDK release after the necessary integration, testing, and validation work is complete.
Note: The React Native SDK follows each native SDK release after the necessary integration, testing, and validation work is complete.
Conclusion
Version 2.36 extends client observability, improves visibility into end-to-end encryption errors, reduces integration complexity with built-in publish retry logic, ensures compatibility with iOS 27, and addresses the October 2026 eMudhra certificate compromise with an updated embedded trust store.
Developers building production video applications will find direct improvements to runtime resilience, diagnostic capability, and multilingual accessibility. We recommend upgrading to 2.36 for all production deployments.












