Issue with ScreenShare: a "track" is received, but not its trackevent related "trackevent".

[Lucas Badico]

Hey guys, if someone could help me with this.

I'm building a service that records audio and video tracks in a WebRTC conference room using the Go programming language and the WebRTC SDK. However, I'm experiencing an issue where the ontrackevent is not being triggered when a new screen is shared in the room. This is preventing me from being able to determine which participant shared the screen.

I have verified that the screen share track is being added to the peer connection and that it has the correct kind and label properties. I have also checked for errors or exceptions that might be thrown when the track is added, but I have not found any. I'm not sure what else could be causing the ontrackevent to not trigger. Any help with this issue would be greatly appreciated.

ion-sdk-go version:

commit: 62ecbcc
Merge: 12e32a5 319347a
Author: adwpc [e-mail]
Date: Mon Jul 11 10:45:23 2022 +0800

Merge pull request #71 from aspnair/master

ion-sfu-rtp example

go version

go version go1.18.1 darwin/arm64

ion version

commit: 17b4053c092cc839844c103c9e09d00829eabf70
Author: Pang [e-mail]
Date: Mon Jul 11 10:02:05 2022 +0800

fix: docker-start-services support multi-times execute (#610)

[Lucas Badico]

Guys, update on this scenario:

When I share my screen before connect my peer that is recording the call, the stream of desktop is as I expected, associated with the user that are streaming.

But when the user start streaming the scream after the recording peer comes to the call, I do not have that information.

Another point, I'm experiencing some irregularities when there are too many people on the call, 2 peers are ok, with 3-4 or more, it becames to lose some connectivity.

The machine dont't look like be the problem, I'm starting to think that these two issue, the screen share without peer information, and the users became lost in the connection, could be related.

If I found more clues, I bring here