Random Video Blackout Issue - All Participants Videos Stop During Active Session except Host

Hi Team,

We’re experiencing a random, non-reproducible issue in our live classroom application where all participants’ videos suddenly stop streaming (go black) during an active Zoom Video SDK session whereas audio remains audible throughout.

Platform:
Classroom : We have a React based application which run through Electron-based desktop application and the zoom session is loaded on electron window by passing the meeting url.
This electron app also includes some of the features which involves creating multiple BrowserWindow instance.

Teacher(HOST): We use the React app directly on browser (generally chrome)

**Flow : **
Each participants including teacher publishes their audio & video when joined. but the video feed of classrooms is only subscribed at teacher end and at classroom end only teacher video feed is subscribed.

during the session no one can turn their video off (We don’t have this feature as per our requirement).
But the teacher can mute/unmute classrooms audio, we do so by calling muteAudio() method at classroom side when it receives socket event to mute and unmuteAudio() to unmute.

So from our end we don’t have any code which can turn the video off.
we are also listening to ‘active-media-failed’ event which is not getting triggered when this issue appear.

Could you please help me in debugging this issue?
What all are the scenario in which zoomSDK stops publishing video stream automatically.

1 Like

Hey @Iqbal1

Thanks for your feedback.

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

Thanks
Vic

Hi @vic.yang

Thanks for your response,

Please find the requested session IDs below.

Session id : p8QEwzsdTtaqZU4vUSKbXQ==
Session Name: 693d6225015dade2f4888f51
Incident Time: 16:52 (IST)

Session Id: Desyy4STS2q1crAhRkJEUA==
Session Name: 693aabcaa34fdf78d566643e
Incident Time: 16:58 (IST)

SessionId : OnVTECLFShuhH5rEo7bmQg==
SessionName: 69384360df92117f4eaabd58
Incident Time: 19:03(IST)

Hi @vic.yang, Did you get the chance to look into this issue?

Hi @Iqbal1

We are investigating this issue and will keep you updated.

Thanks
Vic