[BUG] - Enabling and Disabling video camera on Video Control buttons does not resume the stream for other users in the channel.

[haroonkhan335]

Enabling and Disabling Video camera does not work properly to other users that have joined the channel. When you disable the video camera, it works for all the users including the local user. But when re-enabled, only camera enables for the local user and the stream for other users does not update at all. Though the videoStateChanged callback does calls on all the users devices on the stream.

To Reproduce

1. Run the basic example project with Agora UIKIT and Agora UIKIT control buttons.
2. Disable the video. Works for all users.
3. Enable back the video. Only works for local user and the stream does not get updated for other users on the line.

Expected behavior
Enabling the video should resume the stream for all the users who have joined the channel.

Smartphone (please complete the following information):

• Device: Any Android Device
• OS: Any iOS device.
• Version: latest on pub.dev

[maxxfrazer]

@Meherdeep are you able to replicate this issue?

[haroonkhan335]

@Meherdeep are you able to replicate this issue?

This can be replicated by the simple example from the library.

[Meherdeep]

@haroonkhan335 I tried running the sample code and I was not able to reproduce this error. Can you please share your Agora SDK logs?

[haroonkhan335]

@haroonkhan335 I tried running the sample code and I was not able to reproduce this error. Can you please share your Agora SDK logs?

Logs in terms of what? Agora logs a lot I am not sure which particular you need.

Did you make sure there are multiple users on the video call while testing?

[Meherdeep]

@haroonkhan335 The logs generated while you're trying to disable/enable the local video would be good.

Yes, I tried with multiple remote users on the call.

[Meherdeep]

@haroonkhan335 Sorry, I ran some more tests with cross platform devices and I was able to reproduce this error. We will release a fix for this soon.

[Meherdeep]

@haroonkhan335 Hopefully, the new release fixes this issue. Please give it a try, and feel free to reopen this issue if the issue still persists.