2.34.1.5

OpenTok.Net 2.34.1.5

The release 2.34.1.4 was supposed to be. The façade's own source is identical to it — what changes
here is that it actually ships, and that the Windows pin is no longer readable as something it is
not.

2.34.1.4 was written, reviewed and merged, and then never tagged: merging a release note is what
cuts a release in this repository, and auto-release.yml landed after
docs/release-notes/2.34.1.4.md had already gone in. A note only tags the push that adds it, so
nothing tagged that one, and nuget.org's newest release stayed 2.34.1.3 while Windows support sat
on main unpublished. This note adds itself, which is that mechanism working as intended.

Windows, published this time

Exactly as
2.34.1.4's note
describes it: OpenTokSession, OpenTokPublisher and OpenTokSubscriber run on Windows over
Vonage's OpenTok.Client, with the WinUI renderer supplied by
OpenTok.Net.Win, and both packages carry nine
target frameworks instead of six. Read that note for the two things Windows asks that the other
platforms do not — x64 only, and the first OpenTok object created on the UI thread — and for the
members that are documented no-ops there.

The pin is the pin, not an example of one

Directory.Build.props explained how to point the Windows pin at an in-flight beta by spelling one
out, as a complete OpenTokWinPackageVersion element, in the comment above the pin. MSBuild does
not read comments at all, so the only assignment in the file was the real one: every package this
repository has built was built against the released 2.34.1.4, and the pin itself was never wrong.

Nothing else that reads this file works that way. build/pins.sh, build/check-upstream.sh,
release.yml, pr.yml and this repository's own consistency tests all match the element textually
and keep the first hit, and the first hit was the example. So the daily upstream check reported
OpenTok.Net.Win as pinned to 2.34.1.4-beta.7.3, a prerelease nuget.org has never carried, and —
correctly, for what it believed it was looking at — that the pinned version no longer downloads.
Two findings about a pin that was fine, with the real one invisible behind them.

The example is gone, and RepositoryConsistencyTests now keeps it gone with two checks: every
pinned version property must appear exactly once in Directory.Build.props, comments included, and
every one of them must be a plain release version. The second is the rule the first was hiding — a
released umbrella must not depend on a package built from a branch, so the platform repository
publishes first and this one re-pins behind it, rather than pinning a beta to turn a red leg green.

Pins

Unchanged, and all four confirmed against nuget.org on 2026-07-30 — newest release published, and
the artifact itself downloads rather than merely being indexed:

Property	Package	Version
OpenTokIosPackageVersion	OpenTok.Net.iOS	2.34.1.2
OpenTokAndroidPackageVersion	OpenTok.Net.Android	2.34.1.4
OpenTokWinPackageVersion	OpenTok.Net.Win	2.34.1.4
OpenTokClientPackageVersion	OpenTok.Client	2.34.1

Nothing is waiting on a platform release this time — all four are live, which is the ordering
2.34.1.4's note asks for and 2.34.1.2 is what happens without.

If you are on 2.34.1.3

Upgrade. Nothing to change in your code: no API and no behaviour moved on iOS or Android. What you
gain is a Windows head that was not there before.

Full changelog: v2.34.1.3...v2.34.1.5

Package

Pinned against OpenTok.Net.iOS 2.34.1.2 and OpenTok.Net.Android 2.34.1.4.

Package	Target frameworks	NuGet
OpenTok.Net	net8.0-android34.0, net8.0-ios18.0, net9.0-android35.0, net9.0-ios18.0, net10.0-android36.0, net10.0-ios26.0	2.34.1.5
OpenTok.Net.Maui	net8.0-android34.0, net8.0-ios18.0, net9.0-android35.0, net9.0-ios18.0, net10.0-android36.0, net10.0-ios26.0	2.34.1.5

dotnet add package OpenTok.Net.Maui --version 2.34.1.5

OpenTok.Net.Maui brings OpenTok.Net with it. Take OpenTok.Net alone if you
are not building MAUI and would rather render video yourself.

Licensing

The code in this repository is MIT. OpenTok.Net.iOS and OpenTok.Net.Android, which
this package depends on, each embed Vonage's proprietary OpenTok / Vonage Video API
SDK, which is not open source - see licenses/Vonage-OpenTok-SDK.md.

2.34.1.3

OpenTok.Net 2.34.1.3

A pin bump. No API change, no behaviour change — the façade's own source is identical to 2.34.1.2.

Repoints Android at a version that exists

OpenTokAndroidPackageVersion moves 2.34.1.3 → 2.34.1.4.

2.34.1.2 pinned OpenTok.Net.Android at 2.34.1.3, which was never published. That release train
failed partway through: OpenTok.Net.Transformers.Android was 304 MB against nuget.org's 250 MB
limit and the push was rejected with 413 RequestEntityTooLarge, taking the rest of the train with
it. OpenTok.Net.Android on nuget.org therefore still ended at 2.34.1.2, and this façade's pin —
exact, by design, so a consumer cannot resolve a platform package it was never built against —
pointed at nothing. dotnet add package OpenTok.Net could not restore.

OpenTok.Net.Android 2.34.1.4 is the re-cut of that release, at 167 MB. Its binding content is
unchanged; everything that moved was in the transformers package, which this façade does not
reference.

OpenTok.Net.Android 2.34.1.4 must be on nuget.org before this is published. That ordering
always applied to this repository — the pin is exact and bumped by hand — but it is worth stating
here, because the previous release is the one that proved what happens when the platform package
does not arrive.

OpenTokIosPackageVersion is unchanged at 2.34.1.2, which is current: the iOS train published
cleanly, and OpenTok.Net.iOS 2.34.1.2 and OpenTok.Net.Transformers.iOS 2.34.1.2 are both live.

If you are on 2.34.1.2

Upgrade. There is nothing to change in your code — 2.34.1.2 simply cannot restore.

Package

Pinned against OpenTok.Net.iOS 2.34.1.2 and OpenTok.Net.Android 2.34.1.4.

Package	Target frameworks	NuGet
OpenTok.Net	net8.0-android34.0, net8.0-ios18.0, net9.0-android35.0, net9.0-ios18.0, net10.0-android36.0, net10.0-ios26.0	2.34.1.3
OpenTok.Net.Maui	net8.0-android34.0, net8.0-ios18.0, net9.0-android35.0, net9.0-ios18.0, net10.0-android36.0, net10.0-ios26.0	2.34.1.3

dotnet add package OpenTok.Net.Maui --version 2.34.1.3

OpenTok.Net.Maui brings OpenTok.Net with it. Take OpenTok.Net alone if you
are not building MAUI and would rather render video yourself.

Licensing

The code in this repository is MIT. OpenTok.Net.iOS and OpenTok.Net.Android, which
this package depends on, each embed Vonage's proprietary OpenTok / Vonage Video API
SDK, which is not open source - see licenses/Vonage-OpenTok-SDK.md.