Timeout for addRemoteCandidate. Consider sending an end-of-candidates notification

Question

Timeout for addRemoteCandidate. Consider sending an end-of-candidates notification

Aleksei-Suprun-Mera opened this issue 5 years ago · comments

Hello.

Description

I have the error "Timeout for addRemoteCandidate. Consider sending an end-of-candidates notification" in Edge Microsoft EdgeHTML 18.18363 (Microsoft Edge 44.18362.449.0)

Thanks

SDCRoman · Answer 1 · Mon May 18 2020 19:38:31 GMT+0800 (China Standard Time)

How do you fixed the issue?

Aleksei Suprun · Answer 2 · Mon May 18 2020 19:53:46 GMT+0800 (China Standard Time)

How do you fixed the issue?

I didn't resolve this issue. Edge requires a call addIceCandidate(null) when all remote candidates have been added. If you don't do that this will happen automagically after 3-4 seconds, but that increases the chance of failure.

Aleksei Suprun · Answer 3 · Thu Jul 09 2020 15:33:21 GMT+0800 (China Standard Time)

How do you fixed the issue?

Have you fixed this issue?

SDCRoman · Answer 4 · Thu Jul 09 2020 19:55:40 GMT+0800 (China Standard Time)

How do you fixed the issue?

Have you fixed this issue?

No, it seems it does not work on the old Edge versions. But I noticed that windows recently updates Edge to the chromium based Edge. Hopefully the issue will vanish then.

Kara Isakson · Answer 5 · Thu Aug 06 2020 04:34:20 GMT+0800 (China Standard Time)

I am also running into this issue in Legacy Edge, except I don't get it consistently. I already send a null candidate at the end of candidates which I would have expected to fix this issue. Currently testing in Microsoft Edge 42.17134.1098.0, Microsoft EdgeHTML 17.17134.
Has anyone else been able to make any progress on this or learn anything new about how to work around this?