This message was deleted.
# helpdesks
steep-balloon-41261
01/11/2023, 1:54 PMThis message was deleted.
b
boundless-energy-78552
01/11/2023, 1:56 PMWhen participant is
nilb
brief-refrigerator-69901
01/11/2023, 1:57 PMInteresting, it seems like the Go SDK never adds the participant, even when using as a client.
😮 1
b
boundless-energy-78552
01/11/2023, 1:58 PMcc @dry-elephant-14928
b
brief-refrigerator-69901
01/11/2023, 1:58 PMIll try debugging this a bit more
brief-refrigerator-69901
01/12/2023, 1:13 AMHey @dry-elephant-14928, not sure if you've ran into this issue, but I cannot seem to be able to receive a participant ID from the Go SDK
brief-refrigerator-69901
01/12/2023, 1:19 AMOkay, Sorry, the onDataReceived finally works in Go. Sorry, this was my bad.
brief-refrigerator-69901
01/12/2023, 2:47 AMFrom what I understand and getting is on the Client SDK.. if using GO as Client SDK and it executes a
LocalParticipant.PublishDatabrief-refrigerator-69901
01/12/2023, 2:47 AM@dry-elephant-14928 could you tell me, Is that expected?
d
dry-elephant-14928
01/12/2023, 5:04 AMhmm that's not expected.
dry-elephant-14928
01/12/2023, 5:04 AMclient sdks should behave the same.. it's possible it's a bug with go sdk during publishing
b
brief-refrigerator-69901
01/12/2023, 1:49 PMOkay, I wasn't going crazy then ahah Thanks @dry-elephant-14928
brief-refrigerator-69901
01/14/2023, 4:56 PM@dry-elephant-14928 Finally I found the issue. And its coming from the JS Client Side... In my case, the
participantundefinedbrief-refrigerator-69901
01/14/2023, 5:11 PMI'm wondering if we could maybe have something such as:
Copy code
const participant = !userPacket.participantSid
? undefined
: this.participants.get(userPacket.participantSid)
?? this.createParticipant(userPacket.participantSid);brief-refrigerator-69901
01/14/2023, 7:13 PMFor the time being, this works for me, and I get the participant obj. 🙂 Although my only concern is maybe you guys were only doing the get, to make sure the participant actually exists. 🤷♂️
d
dry-elephant-14928
01/15/2023, 5:24 AM@brief-refrigerator-69901 I think this is the right behavior.. if the publisher is hidden, then we can't really attribute any participant to it.
Actually this seems to be a side effect. it's debatable whether a hidden participant should be able to publish data to others. We currently do not prevent it; but it seems that the behavior is kind of confusing.
b
brief-refrigerator-69901
01/15/2023, 7:13 PMFor me, this is a server state participant, hence the hidden, but this one pushes Data to all or specific participants.
2 Views