Skip to content
This repository has been archived by the owner on Apr 27, 2021. It is now read-only.

DOMException: Failed to execute 'setLocalDescription' on 'RTCPeerConnection': Called in wrong signalingState: kStable #98

Open
Mamong opened this issue Apr 16, 2020 · 0 comments

Comments

@Mamong
Copy link

Mamong commented Apr 16, 2020

I just test the webrtc demo on https://webrtc-from-chat.glitch.me/
I found it works well when firefox calls firefox,chrome calls chrome and firefox calls chrome, but fails when chrome calls firefox. The last logs in chrome console as below:

[1:39:13 PM] *** Adding received ICE candidate: {"candidate":"candidate:0 2 UDP 2122252542 192.168.2.101 59175 typ host","sdpMid":"1","sdpMLineIndex":1}
client.js:56 [1:39:13 PM] Message received:
client.js:128 Object
client.js:56 [1:39:13 PM] *** Adding received ICE candidate: {"candidate":"candidate:3 2 TCP 2105524478 192.168.2.101 9 typ host tcptype active","sdpMid":"1","sdpMLineIndex":1}
client.js:56 [1:39:13 PM] *** ICE connection state changed to connected
client.js:56 [1:39:13 PM] *** WebRTC signaling state changed to: stable
2client.js:56 [1:39:13 PM] *** Track event
client.js:56 [1:39:13 PM] *** WebRTC signaling state changed to: have-remote-offer
client.js:56 [1:39:13 PM] *** ICE gathering state changed to: complete
client.js:56 [1:39:13 PM] *** ICE gathering state changed to: gathering
client.js:605 Uncaught (in promise) DOMException: Failed to execute 'setLocalDescription' on 'RTCPeerConnection': Called in wrong signalingState: kStable

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant