Chromium Instance Freezing/Failing to Load in runRenderingContext (Camera View)

Zoom Apps
1

Hi Zoom developers,

I am developing a Zoom App that utilizes the runRenderingContext method with the “camera” view to overlay dynamic content on the user’s video stream.

While this functionality works correctly for the majority of our users, a subset of customers are experiencing issues where the Chromium instance responsible for rendering the camera overlay either gets stuck and becomes unresponsive or fails to load the application page.

I recently had a session with a client where this behavior was persistent, and the camera overlay never rendered, despite troubleshooting steps like uninstalling/reinstalling the Zoom app, clearing cache, and reinstalling the Zoom client.

I understand that direct developer tools for the “in-camera” Chromium webview are not available. This makes it extremely challenging to diagnose the root cause of these failures. But are there any methods, tools, or hidden flags within the Zoom client that can enable more verbose logging or provide diagnostic traces for the Chromium instance running the camera view?

2

hi @asera79 ,

Sorry you are having issues.
Did you now there is message feature that allows you to send messages to and from the app page and the camera view.
I used this to return log messages to see why the web view has failed.
So I could check for errors, and see if the webview was doing any code.

See if that helps
all the best

John

1 Like
3

Hi John!

Thanks for the tip! I do use the message feature for app-to-camera communication. The problem is, in rare cases, something breaks before the Zoom SDK even initializes, so I can’t use that API.

BR,
Sergey.