Error with multiple offers per RTCPeerConnection setup
See original GitHub issueI have encountered several scenarios where setRemoteDescription
has been called more than once. This can happen if the sdp
message is delayed on its way from one client, to the signalhub, to the second client. This mostly happens in slow networks with a high packet drop rate (e.g. 4G).
This is what’s printed when debug is turned on:
simple-peer [783e416] destroy (error: InvalidStateError: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote offer sdp: Called in wrong state: kHaveLocalOffer) +2ms
Issue Analytics
- State:
- Created 4 years ago
- Comments:9
Top Results From Across the Web
Can I re-use an "offer" in WebRTC for mulitple connections?
In my prototype I see that clicking "create offer" multiple times results in the same string. So, if have client A, and connect...
Read more >Establishing a connection: The WebRTC perfect negotiation ...
Perfect negotiation works by assigning each of the two peers a role ... an offer, we ask WebRTC to select an appropriate local...
Read more >825576 - RTCPeerConnection objects are released too slowly ...
Issue 825576: RTCPeerConnection objects are released too slowly and reallocating causes exception: Cannot create so many PeerConnections.
Read more >WebRTC RTCPeerConnection. One to rule them all, or one ...
What would be the trade-offs between combining multiple streams in 1 connection or setting up multiple connections (e.g. 1 for each stream)?.
Read more >Manage Dynamic Multi-Peer Connections in WebRTC - Medium
The second user, when receiving the offer, will have to do the same thing as first client did: create a RTCPeerConnection associated with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m closing this issue then, but feel free to continue discussion if necessary
It is rather unfortunate but I did not have debug enabled on the other side at that particular point 😩 Will update if this comes up again when I can catch both ends.