fix(client): avoid SFU socket close when online fires without offline recovery#2292
Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughA single early-return guard is added in ChangesReconnect Handler Guard
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
💡 Overview
This PR fixes an issue where a
network: onlineevent could close the SFU WebSocket even though the call had not entered offline recovery. This can happen whennetwork: offlinefires before the call has successfully joined, so no networkAvailableTask is created. Whennetwork: onlinelater fires, the SDK should ignore it instead of closing the active SFU socket with4100.📝 Implementation notes
🎫 Ticket: https://linear.app/stream/issue/REACT-1014/network-change-closes-sfu-socket
📑 Docs: https://github.com/GetStream/docs-content/pull/
Summary by CodeRabbit