Hello, I’m getting weird unexpected behavior from the Vivox service in Unity.
Vivox version: 16.5.3
Unity version: 2020.3.48f1
After subscribing to the participant’s ParticipantMuteStateChanged event, and after muting, unmuting, and muting the participant, the event fires twice. First one has the participant muted and the second one immediately fires but the mute state is false when it should actually stay true.
Here are the steps:
- Subscribe to ParticipantMuteStateChanged event
- Mute player with VivoxParticipant.MutePlayerLocally
- Unmute player with VivoxParticipant.UnmutePlayerLocally
- Mute player again VivoxParticipant.MutePlayerLocally
- Two events fire. First event VivoxParticipant.IsMuted == true, then immediately after VivoxParticipant.IsMuted == false. I’m not able to hear that player at this moment
Expected behavior should be not being able to hear the player and VivoxParticipant.IsMuted == true.
This seems like a bug on the Vivox service side since there is only one call to mute the player, there shouldn’t be two events firing and with the wrong mute state. Can anyone point me in the right direction to solve this? Anyone else running into this? Is this a Vivox service bug?
Thank you!