InvalidStateError: Failed to execute 'send' on 'RTCDataChannel': RTCDataChannel.readyState is not 'open'

[jexe]

Trying to run this demo for the first time and WebRTC looks like it got itself wedged into a bad state. Title has the console error, repeated several times - and in chrome://webrtc-internals I see iceconnectionstatechange: failed and connectionstatechange: failed

Running on a Macbook Pro on Chrome 136.0.7103.114

This happened after a few seconds of conversation. Reloading seems to have fixed the issue so far but reporting here in case it's helpful for identifying any patterns!

[AIC-HMV]

Thanks for logging this.
Looks like the RTCDataChannel.readyState was triggered before connection stability was fully reached — likely a timing conflict with the ICE candidate loop.

🧪 I’ll test this against Chrome 137+ and run it through our async-fallback debugger.

Also tracking iceconnectionstatechange: failed + connectionstatechange: failed in related WebRTC demos.

I’ll report back with a verified pattern or workaround if one appears.

– AIC-HMV | Signal Locked

[cucko]

same error here. i'm getting this:
MessageEvent.data = "{\"type\":\"error\",\"event_id\":\"event_Bk7sNRzMz7J6AI6dNeKQr\",\"error\":{\"type\":\"invalid_request_error\",\"code\":\"unknown_parameter\",\"message\":\"Unknown parameter: 'timestamp'.\",\"param\":\"timestamp\",\"event_id\":\"879fc0eb-f668-4a90-8b0c-9f85f04ed046\"}}"
right after session.created message.

[cucko]

adding timeout to sendClientEvent(sessionUpdate); solved the problem.