but the less i think about the better 🙂

i'd assume most devs are pretty good web developers but not necessarily webrtc ppl

agreed.. client shouldn't have to worry about which one.. but the error should state as such

connected should mean ready to go..

i'll file an issue

yep I was seeing the same behavior regarding the offer negotiation as furqan

also some some other errors that seem to go uncaught ---

OperationError: Failed to execute 'addIceCandidate' on 'RTCPeerConnection': Error processing ICE candidate

this seems to be happening in

client-sdk-js/src/room/RTCEngine.ts

on line 115. I'm not sure if we're supposed to expect this to retry or not but the exception went uncaught ---

InvalidStateError: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable

I've seen this a couple times. Looks like it could be happening on either line 106 or line 121 in the

src/room/RTCEngine.ts

file

and I'm experiencing the same issues as furqan as described on the 2:52AM message

cool, logging these.

I’m particularly curious about

Failed to execute 'setRemoteDescription'

that seems to indicate a negotiation failure.. and could be detrimental to the connection

do you have any logs around it that you could share?

same here. Is it possible that we called

connect

twice? How could the sdp reach state

stable

?

hmm let me see if I can gather some

on the client side? Or server?

on client

that might resolve the streams not subscribed issues

also try the latest 0.2.4 and see if that improves things for you.. it gets rid of a pretty core synchronization issue

trying 0.2.4

can already say that

TrackSubscribed

didn't fire consistently but we were eventually able to sync up

might be an issue on our end

any changes to the js client?

nope, our issues might still be there FWIW.. just thought 0.2.4 is an improvement

will still log & track down other issues.. whenever possible, upload logs here so it’s a bit easier to follow how it got to that state

cool sounds good

is there a reason why this function returns a list of `Publication`s?

unpublishTracks(
    tracks: LocalTrack[] | MediaStreamTrack[]
  ): LocalTrackPublication[] {
    const publications: LocalTrackPublication[] = [];
    tracks.forEach((track: LocalTrack | MediaStreamTrack) => {
      const pub = this.unpublishTrack(track);
      if (pub) {
        publications.push(pub);
      }
    });
    return publications;
  }

line 182

src/room/participant/LocalParticipant.ts

yes.. if you are using the server id to keep track of things

you can ignore it though

got it