User is not send video

Video SDK Web
,
1

Description

I recently upgraded from Zoom Video SDK version 1.12.12 to 2.1.10, and after the update, I’ve started encountering a video-related issue that wasn’t present before.

Issue Observed:

  • When the issue occurs, both participants’ video screens start blinking or flickering.
  • This behavior seems to be triggered most frequently after the user-updated event is emitted.
  • In my implementation, upon receiving the user-updated event, I check which user’s video should be displayed and accordingly update the active video stream using the user’s userId.
  • This issue mostly occurs when the internet reconnects (e.g., after a brief disconnection), which causes the user-updated event to fire.
  • I did not experience this problem with version 1.12.12.

Additional Info:

  • The problem appears to be more prevalent during network interruptions and automatic reconnections.

Browser Console Error
{
“type”: “INVALID_PARAMETERS”,
“reason”: “user is not send video”,
“errorCode”: 6001
}

Which Web Video SDK version?
2.1.10

Video SDK Code Snippets
Applying code as given in new docs.

await stream.startVideo()

let userVideo = await stream.attachVideo(client.getCurrentUserInfo().userId, RESOLUTION)

document.querySelector('video-player-container').appendChild(userVideo)

Troubleshooting Routes
Tried deleting & recreating video player on user-updated event.

Device (please complete the following information):

  • Device: [Windows]
  • OS: [Windows 10]
  • Browser: [Chrome]
  • Browser Version [136.0.7103.114 (Official Build) (64-bit)]

Additional context
I am creating a video call application, with custom web-socket events. Once internet is offline I am handling reconnect part manually using socket events.

2

Hi @meet-jeavio, welcome to the community.

Based on your description, the flickering issue likely results from the order of operations. To improve stability, especially during reconnects, please ensure the following:

1. Bind client events before client.join()

client.on('user-updated', handleUserUpdated);
await client.join(...);

2. Attach local video only after startVideo() resolves, and handle errors properly

stream.startVideo()
  .then(async () => {
    const userId = client.getCurrentUserInfo().userId;
    const videoElement = await stream.attachVideo(userId);
    document.querySelector('video-player-container').appendChild(videoElement);
  })
  .catch((error) => {
    console.error('startVideo error:', error);
    setTimeout(() => {
      stream.startVideo().catch(err => console.error('Retry failed:', err));
    }, 1000);
  });

Also, consider upgrading to Video SDK version 2.2.0 or later, as required for compatibility with Chrome 137+ and Safari 18.4+.

Let us know if this helps resolve the issue.

3

Hey @meet-jeavio

Thanks for your feedback.

Could you share some problematic session IDs with us for troubleshooting purposes?

Thanks
Vic

4

Hello @freelancer.nak ,

Haven’t tried this, will try the same.

Thanks.

5

Hello @vic.yang

We don’t store it, but I just tried right now and following are some of the session IDs:
Hti1fya7SWe0hFh32m6UYg==
37vZVR5XTGqw6OyfFlvNoA==

6

Hi @meet-jeavio

Hti1fya7SWe0hFh32m6UYg==

After analyzing the logs, we found that the camera was occupied by another program, which caused the video capture to fail. As a result, when you called the attachVideo method, you encountered the user is not sending video error.

Thanks
Vic

7

Hi @meet-jeavio

37vZVR5XTGqw6OyfFlvNoA==

UserIDs 16779264, 16780288, and 16781312 all experienced the same camera issue as described above.

Could you please confirm whether they were running on the same machine, with the host using the camera while other browser instances also attempted to access it?

If so, this would explain the issue. On Windows, the camera is exclusive-use, meaning it cannot be shared by multiple applications at the same time.

Thanks
Vic

8

Hello @vic.yang

For Hti1fya7SWe0hFh32m6UYg== that could be that case.

But for 37vZVR5XTGqw6OyfFlvNoA== that wasn’t the case as calls were joined from different devices.

Thanks,
Meet

9

Hello @vic.yang,

Did you find anything else?

Thanks,
Meet