Hi. I believe when live custom streaming was integrated to the Meeting SDK Web that when a host changes the screen format say from speaker to gallery that the live custom stream follows (it works in the client). We recently moved from anglerjs to react 9 and are finding that component view (haven’t implemented or tested client view) it does not follow.
This forces us to manual each session move rights to the client software host to change view and then back to web user as host and it will follow for that session until ended.
Please advise if this is known and there is a coming fix. Our priority is for Reactjs component view.
It would also be helpful to know if it works in angler but not react or in client view but not component view. As you can imagine this limits adoption and use of Meeting websdk. Thanks.
Based on Zoom’s public docs, I’d treat this as an undocumented behavior gap rather than a confirmed React migration issue. Zoom supports custom livestreaming and the Meeting SDK Web has both Client View and Component View, but I don’t see a documented guarantee that the livestream compositor follows the host’s selected speaker or gallery layout from Component View.
For teams that need a more controlled meeting capture pipeline, Recall.ai’s Meeting Bot API can help avoid depending on Web SDK UI layout behavior.
@amanda-recallai Are you replying to help solve that your product can fix the custom live stream host view follow? thanks. I am looking for zoom support answer as to functionality.
Following up—this issue remains unanswered after ~1 month.
Can someone from Zoom confirm whether this is being reviewed, or if I need to escalate and pay for paid support if you have a monthly option or ?
If the developer forum is not monitored for timely responses on SDK issues, please clarify expectations. This is a blocking issue for our implementation.
Thank you for the detailed report; it helps us understand the issue better.
To help us debug and guide you further, could you please share the following:
Browser DevTools Console logs - Any errors or warnings that appear when the host switches the view (Speaker to Gallery or vice versa) while live streaming is active.
Network tab logs - Any failed or unexpected API/WebSocket calls around the time the view change happens.
SDK version - The exact version of the Zoom Meeting SDK for React you are currently using.
Any event listeners - If you have any event handlers set up for view/layout changes, sharing those code snippets would be helpful.
To open DevTools in Chrome: press F12, go to the Console tab, reproduce the issue, then copy/paste any relevant logs here.
This will help us narrow down whether the issue is on the SDK event side or the streaming configuration side.
Naeem - sorry this is clouding my issue that needs response from internal Zoom developer support team not freelancers or pasting generic trouble shooting questions off topic. Thank you.