Description We’re using Puppeteer to launch a Chrome instance with the --use-fake-device-for-media-stream flag. However, we occasionally encounter an issue where the speaker doesn’t work—we can’t hear the other participants speaking. Upon checking the Zoom management page, we found that the microp…

[image] Vic: After analyzing the logs, we found that the user experienced significant delay, which could be the cause of the video render issue. @vic.yang Could you help troubleshoot whether the delay was caused by a Zoom SDK problem, a network issue, or resource limitations on the client …

Hi @lmtruong1512 rsNXr1RbS0uTT1p+GkzrKA== Around 5 minutes after the session started, the uplink and downlink of UserID: 16778240 dropped sharply, which could be the cause of the video issue. Thanks Vic

@vic.yang Could you help investigate the issue where both the microphone and speaker are not accessible for the RECORDING_BOT when starting audio with the speakerOnly option set to true in the following sessions: 9aF8YPhEQgaHxr4hoZwG3w== UsIoxcsDSgerPxuK2NZwIQ== await state.mediaStream.startAudio…

@vic.yang In that case, is the RECORDING_BOT able to hear other participants speaking?

Hi @lmtruong1512 9aF8YPhEQgaHxr4hoZwG3w== UsIoxcsDSgerPxuK2NZwIQ== After analyzing the logs, these two BOT users did not successfully start audio, possibly due to the browser’s autoplay policy requiring user interaction. You can listen for the auto-play-audio-failed event. [image] Vi…

Hi @lmtruong1512 If stream.startAudio is called immediately upon joining a session, it might fail. Use the auto-play-audio-failed event to get notified of this issue so you can prompt users to interact with the page to restore audio. ‘Called immediately upon joining a session’ here means there’s…

@vic.yang Thank you for the response. May I ask a bit more? Is it possible that startAudio sometimes doesn’t return an error directly, and instead we need to listen for the auto-play-audio-failed event? Similarly, for video — in cases where errors aren’t caught by startVideo,…— how should I handle …

Hi @lmtruong1512 startAudio has a timeout mechanism — if it fails to join audio within 40 seconds, it will return a timeout error. When auto-play requirements aren’t met, the Video SDK interrupts the join process and emits the auto-play-audio-failed event. In that event, simply guiding the user to…

@vic.yang Continue follow the reason why BOT users sometimes fail to start audio: it may be due to the browser’s autoplay policy, which requires user interaction before playing audio. To start a BOT joining a meeting, we launch a separate EC2 instance for each BOT using a headless browser, whic…

The speaker sometimes does not work when using Puppeteer with a fake media device

Video SDK Web

lmtruong1512 (TruongLM) May 12, 2025, 8:57am 13

@vic.yang Do you know why this happens randomly with the same code? Could it be related to the timing of the startAudio call — maybe it’s being called too soon?"

Topic		Replies	Views
Audio does not start, same user authorizing Web	17	2824	August 21, 2020
Mobile audio issues (safari & chrome) Web	41	2895	July 23, 2023
Have to click on the "startAudio button" twice in Linux/Chrome Web video-sdk	2	55	September 6, 2024
Handling the active-share-change event when one joins the channel after someone shared the screen Web	199	4667	December 21, 2022
Participant can't hear anyone after joining a session Web	4	536	October 13, 2022

The speaker sometimes does not work when using Puppeteer with a fake media device

Related topics