Mute and unmute are not reflected in other users

[vedartm]

Describe the bug To find who is muted and who is unmuted, I am using remoteAudioStateChanged but it is not reliable at all. When someone mutes or unmutes I am only getting reason as AudioRemoteStateReason.NetworkCongestion or AudioRemoteStateReason.NetworkRecovery or AudioRemoteStateReason.Internal Instead of AudioRemoteStateReason.RemoteMuted or AudioRemoteStateReason.RemoteUnmuted How do I fix this?

To Reproduce Steps to reproduce the behavior:

1. Start an audio channel.
2. Ask more than 2 people to join
3. Try muting and unmuting
4. Check if it is reflected in other users

Expected behavior It is supposed to send AudioRemoteStateReason.RemoteMuted or AudioRemoteStateReason.RemoteUnmuted when mute or unmute happens accordingly.

[RoJoHub]

After my test, the event can be triggered normally Could you please provide a example?

[kameshkarthi]

Try this one,

audioSubscribeStateChanged: (channel,uid,oldState,newState,elapse){ if(newState == Rtc.StreamSubscribeState.Subscribed){ //Un mute } else if(newState == Rtc.StreamSubscribeState.NoSubscribed){ //mute } }

[RoJoHub]

Sorry Can you provide an example for verification? Because after my test, I found that this problem did not occur. I will close this issue

[vedartm]

@RoJoHub How do I demonstrate the issue?

[devsideal]

Facing the same issue with group video call, eg:- [ A ]

engine.muteRemoteAudioStream(B, true);
remoteAudioStateChanged: (-,-,reason,-) {  print("Reason: $reason")  }

[ B ]

remoteAudioStateChanged: (-,-,reason,-) {  print("Reason: $reason")  }

With this code, I'm expecting, when user A mute the user B then user B should notify with reason Muted, but not getting the expected result:

When A perform mute action for B: Nothing print on B, instead A receives reason LocalMuted and RemoteMuted.

What I'm doing wrong? Or Is there any other way to achieve the same?

[littleGnAl]

If you still face issues, please try upgrading to the new version to see if it works for you.

[github-actions[bot]]

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. If you find this problem please file a new issue with the same description, what happens, logs and the output. All system setups can be slightly different so it's always better to open new issues and reference the related ones. Thanks for your contribution.

[github-actions[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please raise a new issue.