-
Notifications
You must be signed in to change notification settings - Fork 94
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
[iOS] Releasing ACSRenderer
removes ACSRemoteVideoStream
as well
#95
Comments
Disposing From the issue it seems you are talking about the |
Hey @sankum-msft thanks for the response! My observation was based off on To add a bit more context here, I am attempting to dispose the renderers of remote participants when I background my app, in order to avoid any unnecessary overhead while the app is in the background. When I foreground the app, I wanted to create new renderers with the existing remote participants' Here are the exact repro steps:
|
There is a known bug in ACS Calling SDK is not raising |
We've released beta6 that should fix this issue. |
Closing. Please let us know if you encounter this problem again. |
Describe the bug
Disposing and releasing my reference to an
ACSRemoteParticipant
'sACSRenderer
causes the associatedACSRemoteVideoStream
to be removed as well. In other words, the stream no longer appears in thevideoStreams
array maintained by the remote participant.Expected behavior
I would expect that the removal/disposal of an
ACSRenderer
should not have an effect on anACSRemoteVideoStream
. For instance, it would be nice to be able to dispose the current renderer but re-use the remote video stream at another time and initialize a new renderer object with it.The text was updated successfully, but these errors were encountered: