You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The call is not initiated and the following is printed to the log:
[io.getStream.chat.core.web_socket_engine_queue] [WebSocketClient.swift:216] [webSocketDidReceiveMessage(_:)] > keyNotFound(CodingKeys(stringValue: "user", intValue: nil), Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: "user", intValue: nil) ("user").", underlyingError: nil))
GetStream Environment
GetStream Video version: 1.14.1 GetStream Video frameworks: StreamVideo, StreamVideoSwiftUI iOS version: 18.2 Swift version: 5 Xcode version: 16.2 Device: iPhone 16
Additional context
This had not occurred previously but without any code updates it has suddenly appeared. Same behavior with Stream Video 1.0.9 as well, so doesn't seem to be new with the new version.
The text was updated successfully, but these errors were encountered:
What did you do?
User initiates a Stream Video call.
What did you expect to happen?
The call to start without error.
What happened instead?
The call is not initiated and the following is printed to the log:
[io.getStream.chat.core.web_socket_engine_queue] [WebSocketClient.swift:216] [webSocketDidReceiveMessage(_:)] > keyNotFound(CodingKeys(stringValue: "user", intValue: nil), Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: "user", intValue: nil) ("user").", underlyingError: nil))
GetStream Environment
GetStream Video version: 1.14.1
GetStream Video frameworks: StreamVideo, StreamVideoSwiftUI
iOS version: 18.2
Swift version: 5
Xcode version: 16.2
Device: iPhone 16
Additional context
This had not occurred previously but without any code updates it has suddenly appeared. Same behavior with Stream Video 1.0.9 as well, so doesn't seem to be new with the new version.
The text was updated successfully, but these errors were encountered: