After upgrading to 2.3.0: Video was interrupted by the system. Please click anywhere to resume

Video SDK Web
1

Description
I noticed that a few days ago a new version of Video SDK for Web was released: v2.3.0. After updating from v2.2.12, the participant’s camera feed doesn’t work at all (self-view).

Every time this error appears:

{
    "message": "Video was interrupted by the system. Please click anywhere to resume.",
    "type": "video",
    "code": 207
}

I checked it on Chrome.

Has something changed? Should I enable the participant’s camera differently? Currently I do it automatically, i.e. I enable it automatically after creating the component with Video SDK. I’m using WebRTC and attachVideo.

Session ID: SapZ5ALFQ1S0GLndWRjTIQ==

1 Like
2

Hi @klocuszek a couple of questions so I can better assist here:

  • Do you experience this issue on other browsers?
  • Can you include a code snippet of your attachVideo logic?
  • When you or the participant click the screen on the affected device, does the video start as expected? If so, this might be a security requirement by the browser for user interaction before media peripherals are turned on.
1 Like
3

Hey @klocuszek

Thanks for your feedback.

SapZ5ALFQ1S0GLndWRjTIQ==

After analyzing the logs, we found that this event was triggered by the browser and may be related to automatically starting video without interacting with the page. However, we still need to confirm the following factors:

  1. Is there another application also using the same camera?

  2. Was the browser switched to the background, such as switching tabs or minimizing the window?

Thanks
Vic

1 Like
4

Hi, Vic! Thanks for your reply. I think there was something wrong with the camera. After shutting down the browser, the camera LED was still visible, as if another process was using it, and that was probably the problem. After rebooting, I can’t reproduce this error.

1 Like
5

However, this error still appears. What is your advice in this case? Should I not turn on the meeting attendees’ camera automatically, but always wait for them to turn it on by themselves using the button?

1. Is there another application also using the same camera?
No.

2. Was the browser switched to the background, such as switching tabs or minimizing the window?
No.

6

Hey @klocuszek

We don’t have any further findings at the moment. Could you please try the following:

  1. Check whether the issue disappears when using a different camera device.

  2. Check whether the issue still occurs if the user starts their video only after clicking.

Thanks
Vic

1 Like
7

It turned out that the Android tablet is the culprit. Every once in a while, Samsung’s system process takes over access to the camera for 1-2 seconds, so the 207 code reported by the Video SDK is correct.

8

Hi @klocuszek

I really appreciate you sharing this information with us — it will be very helpful for troubleshooting future issues.

Thanks
Vic