Re: [webrtc-pc] addIceCandidate may not need to throw an error when no remoteDescription (#2519)

This happens in practice when the path for signaling candidates and the path for signaling state updates are uncoordinated, so that a remote candidate may race a remote description.

Stats show that rejection because of no remote description happens in 0.197% of AddIceCandidates calls. It's by far the most common reason for failed AddIceCandidates calls.

GitHub Notification of comment by alvestrand
Please view or discuss this issue at using your GitHub account

Received on Thursday, 30 April 2020 13:40:39 UTC