Use development token source instead of deprecated sandbox - #43
Merged
Merged
Conversation
MaxHeimbrock
force-pushed
the
max/use-development-token-source
branch
from
September 24, 2026 08:49
3a9728b to
c33694f
Compare
MaxHeimbrock
added this pull request to stack #45
September 24, 2026 08:52
MaxHeimbrock
changed the title
MaxHeimbrock
marked this pull request as ready for review
September 24, 2026 15:41
davidliu
approved these changes
Sep 24, 2026
- @livekit/react-native 2.12.0 -> 3.0.0 - @livekit/react-native-webrtc 144.1.2 -> 144.2.0 (required by 3.0.0) - livekit-client 2.21.0 -> 2.22.3 3.0.0 switches to the LiveKit-prefixed WebRTC builds (LiveKitWebRTC pod on iOS, io.github.webrtc-sdk:android-prefixed on Android). The JavaScript API is unchanged, so no app code changes are needed for the SDK bump. The Expo plugin is already at 1.0.3 on the SDK 57 base, the first release that accepts the 3.x SDK as a peer dependency. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
TokenSource.sandboxTokenServer is deprecated since livekit-client 2.22.0 in favor of developmentTokenServer. Same endpoint and behavior, new name. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
LiveKit Cloud and the client SDKs now call this the development token server, matching the Flutter starter. Rename sandboxID to tokenServerId, update the README wording and docs link, and fix the post-create task, which pointed at hooks/useConnection.ts (the file is .tsx) and substituted the old variable name. The task accepts LIVEKIT_TOKEN_SERVER_ID and falls back to LIVEKIT_SANDBOX_ID. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
MaxHeimbrock
force-pushed
the
max/use-development-token-source
branch
from
September 24, 2026 16:46
c33694f to
bd42970
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Found a build issue with the new Xcode, solved here:
This PR bumps the SDK versions and then uses the new development token source instead of the sandbox token source.