Luke Oliff

I've seen this posted by others using React Native. I am not a native app engineer so I have no way to reproduce this. It is likely something to do...

As mentioned we don't support React Native on this SDK yet. It is open source, so we welcome the community to dig into this

Yes, this isn't solvable in the SDK. Even if we queued the messages, there is still a race condition in the transmit. The only recourse is to experiment with an...

I can also reproduce this @sashabaranov ```go var req openai.ChatCompletionRequest if err := json.NewDecoder(r.Body).Decode(&req); err != nil { log.Warn().Err(err).Msg("malformed JSON request") return } ``` Request body is the very same...

A temporary workaround: ```go // Handle response format conversion if present if req.ResponseFormat != nil { openaiReq.ResponseFormat = &openai.ChatCompletionResponseFormat{ Type: openai.ChatCompletionResponseFormatType(req.ResponseFormat.Type), } if req.ResponseFormat.JSONSchema != nil { openaiReq.ResponseFormat.JSONSchema = &openai.ChatCompletionResponseFormatJSONSchema{...

Interesting. I expect it is to do with how it is parsed using the `URL` class in JavaScript

Hmm thinking more about this. We're trying to normalise the URL string for when we add it to the object. Is there a reason you need the trailing slash at...

React Native is not yet supported. I will leave this open in case someone is able to help

This is strange, as our real-time examples work in testing. I wonder if this somehow runtime specific, too? This was our change in this SDK https://github.com/deepgram/deepgram-js-sdk/blob/main/src/packages/AbstractLiveClient.ts#L139-L146

That's odd, as we use `ws` for node runtime websockets in the SDK. Can you tell me anything else about your environment?