.addStream removed

Just admittedly blindly updated react-native-webrtc to

"react-native-webrtc": "^106.0.0-beta.3",

Noticed a bunch of API changes. addStream, getLocalStreams removed.

As the repo stands, if a new user installs this lib and follows the Guides, they will be in for many surprises 😄

Any migration/updated docs planned?

[saghul]

@saghul

In 106 there doesn’t seem to even be a stream in the ontrack event .

There is a list of streams in event.streams, if you set the stream IDs on the other side when you add the transceiver.

Is this expected? Or is there a signaling issue?

Stream-less tracks are possible but rate, that’s why we have that limitation for now.

How are you supposed to use remote tracks if not to add them to streams?

If you set stream IDs when creating your transceiver, or pass the stream when calling addTrack the remote will receive a track that is attached to a stream.

I got something working somehow with:

      PeerConnection.ontrack = (event: any) => {

        PeerConnection?.addTransceiver(event.transceiver, myRemoteStream);

        myRemoteStream.addTrack(event.track);

      };

That’s completely broken. I suggest you read bout the transceivers API on MDN.

Not even sure why or how this works. Investigating further, any help appreciated

[8BallBomBom]

There will eventually be some decent example apps that should help a lot more but most of what is documented currently is pretty straight forward to some extent 👍🏻