Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[bug]Early reconnect during the initial room connection

Open
  • Is something wrong?
#1,189 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@hiroshihorie is already working on this.

Since Sep 4, 2026.

Assessment

This issue has not been assessed yet.

Description

Describe the bug

During the initial room connection, the initial RTC WebSocket closes while Room.connect is still waiting for the PeerConnection to become connected. The SDK starts an automatic reconnect and opens a second RTC WebSocket approximately 170 ms later, while the original connection attempt is still pending. The original attempt eventually fails after approximately 10 seconds with MediaConnectException.

The two observed RTC WebSocket URLs were:

Initial connection:

wss://<host>/rtc?auto_subscribe=1&adaptive_stream=1&protocol=16&client_protocol=1&sdk=flutter&version=2.11.0&network=wifi&os=android&os_version=16&device_model=PJZ110

Reconnect attempt:

wss://<host>/rtc?auto_subscribe=1&adaptive_stream=1&reconnect=1&reconnect_reason=1&sid=PA_3HVH5rf53iDv&protocol=16&client_protocol=1&sdk=flutter&version=2.11.0&network=wifi&os=android&os_version=16&device_model=PJZ110

To Reproduce

  1. Use an Android 16 real device on Wi-Fi.
  2. Use livekit_client 2.11.0 and connect to a room.
  3. Capture WebSocket traffic with Reqable.
  4. The issue was observed only during a specific period. During that period, approximately 1 in 5 connection attempts reproduced it. It was not reproduced before or after that period, including during other Reqable captures. The issue is not currently reproducible on demand.
  5. In a failing attempt, observe the initial RTC WebSocket without reconnect parameters, followed by a second RTC WebSocket containing reconnect=1, reconnect_reason=1, and sid before the initial connection finishes.
  6. The initial connection then fails with MediaConnectException after approximately 10 seconds.

A minimal research test can force the same ordering by controlling the completion order of the WebSocket and PeerConnection operations. The main reproduction is covered by automatic reconnect starts while the initial Engine.connect still waits for PeerConnection; the trigger and key assertions are at lines 199-207.

Expected behavior

The initial room connection should finish successfully or fail before an automatic reconnect creates another RTC WebSocket. The initial connection and the automatic reconnect should not overlap within the same connection flow.

Platform information

  • Flutter version: Flutter 3.38.10 (Dart 3.10.9)
  • Plugin version: livekit_client 2.11.0
  • Flutter target OS: Android, real device (PJZ110)
  • Flutter target OS version: Android 16
  • Flutter console log: The connection state reports disconnected with reason signal; the original attempt later reports MediaConnectException: Timed out waiting for PeerConnection to connect, please check your network for ice connectivity.
Dominant language
Dart
Stars
421
Forks
260
Avg merge
3d 9h
Merged PRs (30d)
11

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from livekit/client-sdk-flutter

All issues in livekit/client-sdk-flutter

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.