iceconnectionstatechange event difference in M73

[Colin Schworer]

Hi,

I'm seeing a difference I don't understand between Chrome M72 and M73.

If I block UDP/TCP for the TURN servers (when they need to be used)...

In Chrome M72

The RTCPeerConnection's ICE agent fires the iceconnectionstatechange event with the iceConnectionState "checking".

This event is eventually followed up by the same event with the iceConnectionState "failed".

In Chrome M73

Only ever get the "checking" event and never get the "failed" event.

Anyone know why this is happening or how to get the "failed" event to fire in Chrome M73 (currently in Beta)

Kind regards,

Colin

[Philipp Hancke]

you might want to check https://bugs.chromium.org/p/chromium/issues/detail?id=922588 -- there were some changes, possibly the scenario you're testing (initial failure?) has not been tested?

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/0758567e-83b1-4e97-a5a6-73a45e2c52e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Philipp Hancke]

its busted apparently. Filed https://bugs.chromium.org/p/chromium/issues/detail?id=933786