[StreamCore] Use core WebSocket state for SFU#1204
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 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 |
SDK Size
|
Public Interface🚀 No changes affecting the public interface. |
StreamVideo XCSize
Show 184 more objects
|
StreamVideoSwiftUI XCSize
|
940e94e
into
iliaspavlidakis/ios-1816-migrate-sdk-signaling-core-infra-onto-stream-core-swift
🎯 Goal
Remove the video-owned
SFUConnectionStatewrapper and useStreamCore.WebSocketConnectionStatedirectly in the SFU/WebRTC path.📝 Summary
SFUConnectionState.SFUWebSocket,SFUAdapter, and WebRTC coordinator context toWebSocketConnectionState.🛠 Implementation
SFUWebSocketnow publishes StreamCore'sWebSocketConnectionStatedirectly.SFUAdaptermirrors that state without conversion, and the joined-stage context storesWebSocketConnectionState.DisconnectionSource.The SFU error handling now unwraps StreamCore client errors at the existing coordinator boundary instead of relying on the removed SFU-specific wrapper.
🎨 Showcase
N/A. Internal migration only.