GetStream / stream-chat-swift

💬 iOS Chat SDK in Swift - Build your own app chat experience for iOS using the official Stream Chat API
https://getstream.io/chat/sdk/ios/
Other
845 stars 204 forks source link

Chat messages failing decoding in SDK.. production down #1678

Closed basememara closed 2 years ago

basememara commented 2 years ago

What did you do?

The chat is broken and seems to be on the GetStream server-side. This is the error that's coming back in the logs from production apps in the field (and local debug versions). Did GetStream change the shape of endpoints without updating the SDKs or provide backwards-compatibility?

What did you expect to happen?

No errors and chat working.

What happened instead?

No chat loads for users and errors message is:

2021-12-09 10:52:28.272 [ERROR] [com.apple.NSURLSession-delegate] [RequestDecoder.swift:75] [decodeRequestResponse(data:response:error:)] > valueNotFound(Swift.KeyedDecodingContainer<StreamChat.UserPayloadsCodingKeys>, Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "channels", intValue: nil), _JSONKey(stringValue: "Index 1", intValue: 1), CodingKeys(stringValue: "messages", intValue: nil), _JSONKey(stringValue: "Index 21", intValue: 21), MessagePayloadsCodingKeys(stringValue: "quoted_message", intValue: nil), MessagePayloadsCodingKeys(stringValue: "user", intValue: nil)], debugDescription: "Cannot get keyed decoding container -- found null value instead.", underlyingError: nil))

GetStream Environment

GetStream Chat version: 4.5.1 GetStream Chat frameworks: StreamChat, StreamChatUI iOS version: 15.1 Swift version: 5.5 Xcode version: 13.1 Device: iPhone 13

Additional context

No code changes happened on our side; GetStream messages started failing for over a day+

b-onc commented 2 years ago

Hello @basememara

You're correct, this is a backend error. Backend is working hard on fixing it - we're expecting this issue to be resolved very soon (less than an hour)

martinmitrevski commented 2 years ago

Hello @basememara,

The issue is resolved now. We are sorry for the inconveniences.