Files
livekit/pkg/rtc
Raja Subramanian 81f41aca20 Full reconnect on publication mismatch on resume. (#1823)
* Full reconnect on publication mismatch on resume.

It is possible that publications mismatch on resume. An example sequence
- Client sends `AddTrack` for `trackA`
- Server never receives it due to signalling connection breakage.
- Client could do a resume (reconnect=1) noticing signalling connection
  breakage.
- Client's view thinks that `trackA` is known to server, but server does
  not know about it.
- A subsequence offer containing `trackA` triggers `trackInfo not
  available before track publish` and the track does not get published.

Detect the case of missing track and issue a full reconnect.

* UpdateSubscriptions from sync state a la cloud

* add missing shouldReconnect
2023-06-24 19:18:05 +05:30
..
2023-03-25 23:17:04 -07:00
2023-03-05 12:55:04 +05:30
2023-04-20 14:15:30 +08:00
2023-02-15 16:47:38 -08:00
2022-01-19 02:13:06 -08:00
2022-03-30 13:49:53 -07:00