Upgrade LiveKit dependencies

[kraenhansen]

Summary

• Upgrade direct LiveKit dependencies to current stable versions that satisfy the repo's 7-day release-age policy:
  • livekit-client to ^2.19.1
  • @livekit/react-native to ^2.11.0
  • @livekit/react-native-expo-plugin to ^1.0.2
  • @livekit/react-native-webrtc to ^144.1.0
• Merge current main into the branch and revert the temporary compatibility changes from Fix WebRTC connection by pinning livekit-client to 2.16.1 #782 now that the service is on LiveKit server 1.12.0:
  • remove the exact livekit-client@2.16.1 pin
  • remove singlePeerConnection: false from Room construction
  • remove the local livekit-client patch registration/file
• Regenerate pnpm-lock.yaml without LiveKit patch metadata.

Validation

• pnpm install --frozen-lockfile
• pnpm build (Node 24 / lts/Krypton)
• pnpm lint (Node 24 / lts/Krypton)
• pnpm --filter @elevenlabs/react-native check-types
• git diff --cached --check

Notes

• Local full/client test runs were blocked by the VM missing Playwright Chromium after the browser installer hung post-download. CI runs tests in the Playwright container image, so the pushed branch is relying on CI for the browser-backed test job.

Slack Thread

  

[kraenhansen]

Checked out the branch locally and ran the example which is exhibiting the symptoms from #661 and #766 - we need to solve that first.

[kraenhansen]

It's my current understanding that we're blocked on upgrading the LiveKit SDKs as they introduced changes which aren't backwards compatible with the server, we're currently working on upgrading the server to unblock this upgrade.

[kalvin807]

we might not need the git patch after the bump. (see #532)
upstream fixed the bug livekit/client-sdk-js#1858

[zacharytyhacz]

Is this still in progress?

[kraenhansen]

@kalvin807 can you help me verify that the patch is no longer needed? I agree this seems to be the case (with webrtcHacks/adapter#1177 (comment)) but then this issue popped up 🤔 webrtcHacks/adapter#1194