Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Android]: call.isMuted() always returns false in call.addOnIsMutedChangedListener() when muted remotely by host #995

Closed
ankiarora opened this issue Jan 28, 2022 · 4 comments
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team

Comments

@ankiarora
Copy link

Description
When a user unmutes himself on android app and then is muted remotely from the Teams app by the host, call.addOnIsMutedChangedListener() listener is called, but inside this listener, call.isMuted() always returns false.

Steps to reproduce the behavior:

  1. User on an android app implementing ACS SDK (2.0.0) joins the meeting
  2. User is accepted to the call by a host.
  3. User unmutes the call.
  4. Host mutes the user from the Teams app.
  5. call.addOnIsMutedChangedListener() is called, and user gets muted. But, call.isMuted() inside this listener remains false.
  6. Expected: call.isMuted() should return true.

Code Snippet
call.addOnIsMutedChangedListener(propertyChangedEvent -> {
Log.i(TAG, "Call ID[" + call.getId() + "] has " + (call.isMuted() ? "" : "NOT ") + "been MUTED");
//call.isMuted() returns false
});

Expected behavior
call.addOnIsMutedChangedListener(propertyChangedEvent -> {
Log.i(TAG, "Call ID[" + call.getId() + "] has " + (call.isMuted() ? "" : "NOT ") + "been MUTED");
//call.isMuted() should return true once host mutes the user from Teams app
});

Setup (please complete the following information):

  • OS: Android
  • IDE : Android Studio
  • Version: 2.0.0

Additional context
The listener was working as expected in version 1.2.1-beta.1. This issue exists in all the versions after 1.2.1-beta.1

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 28, 2022
@vcolin7
Copy link
Member

vcolin7 commented Feb 1, 2022

Hi @ankiarora, thanks for letting us know about this. I will route this to the right person to look at. Just to make sure, this is in reference to the com.azure.android:azure-communication-calling:2.0.0 package right?

@vcolin7 vcolin7 assigned vcolin7 and jsaurezlee-msft and unassigned vcolin7 Feb 1, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Feb 1, 2022
@vcolin7 vcolin7 added bug This issue requires a change to an existing behavior in the product in order to be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Feb 1, 2022
@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Feb 1, 2022
@vcolin7 vcolin7 removed the ACS label Feb 1, 2022
@ankiarora
Copy link
Author

@vcolin7, Thank you for replying. Yes, that's correct.
I realized that this issue did not occur in com.azure.android:azure-communication-calling:1.2.1-beta.1. However, the recent version 2.0.0 is having this issue. Please look into this issue.
Thank you.

@jsaurezlee-msft
Copy link
Member

Hi @ankiarora, thanks for the report. This issue has been fixed and will be published in our next release.

@paolo-ermit
Copy link

This one is working correctly in version 2.1.0

@vcolin7 vcolin7 closed this as completed May 6, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Projects
None yet
Development

No branches or pull requests

4 participants