Same issue as reported here but maybe it belongs here instead?
Hello and thank you for this great service and library!
I found and issue muting participants in a meeting when the userId is included in the meeting token.
Expected behavior
As a user joining with token including owner: true and userId: "some-user-id" I should be able to mute other participants joining with tokens including owner: false and userId: "some-other-user-id"
Describe the bug (unexpected behavior)
When creating a token, via the api or self signed, and including the userId I get update setAudio can't be applied to participant {{userId}}; skipping null when as an owner calling updateParticipant on the daily call object like
Same issue as reported here but maybe it belongs here instead?
Hello and thank you for this great service and library!
I found and issue muting participants in a meeting when the userId is included in the meeting token.
Expected behavior
As a user joining with token including
owner: true
anduserId: "some-user-id"
I should be able to mute other participants joining with tokens includingowner: false
anduserId: "some-other-user-id"
Describe the bug (unexpected behavior)
When creating a token, via the api or self signed, and including the
userId
I getupdate setAudio can't be applied to participant {{userId}}; skipping null
when as an owner callingupdateParticipant
on the daily call object likeIf I exclude the
userId
from the token it works.This is how we create tokens:
Is this expected behaviour? I could not find anything in the documentation about excluding
userId
from tokens for the owner to be able to mute others.