EVERYTHING IS CONNECTING FULLY BUT THEY ARE SIMPLY NOT CONNECTING. WHAT DOES IT MEAN WHEN A WEB RTC CONNCETION HAS A
CONNECTION STATE OF 1,
GATHERING STATE OF 2,
AND A SIGNALING STATE OF 0?
(FIXED) TLDR; add remote ice last
EVERYTHING IS CONNECTING FULLY BUT THEY ARE SIMPLY NOT CONNECTING. WHAT DOES IT MEAN WHEN A WEB RTC CONNCETION HAS A
CONNECTION STATE OF 1,
GATHERING STATE OF 2,
AND A SIGNALING STATE OF 0?
(FIXED) TLDR; add remote ice last
Do the more advanced examples help at all?
MAKE SURE YOU SET THE REMOTE SESSION DESCRIPTION BEFORE ADDING THE REMOTE ICE CANDIDATE. My code was fixed by swapping this:
peer_connection.add_ice_candidate(ice_cand.mid_name, ice_cand.index_name, ice_cand.sdp_name)
peer_connection.set_remote_description(sesh.type, sesh.sdp)
INTO THIS:
peer_connection.set_remote_description(sesh.type, sesh.sdp)
peer_connection.add_ice_candidate(ice_cand.mid_name, ice_cand.index_name, ice_cand.sdp_name)
I have asked them to include a warning for this in the docs, as I was completely unaware you had to do it in a certain order and it does not tell you.