Runaway process created using Layers API

[MaxM]

@victoriaolanipekun

Manipulating the UI this is what I’m

Thanks for sending that my way! Looking at the reference it doesn’t look like that option is supported:

https://marketplace.zoom.us/docs/zoom-apps/js-sdk/reference/#installation

I’ll work with our documentation team to make sure that our documentation matches the current version of our code.

@victoriaolanipekun

Camera mode never gets initiated on my mac after calling runRenderingContext with options { view: “camera” }. If I change the view value to immersive { view: “immersive” }, I can see that the runningContext changes to “inImmersive” mode whereas I do not get “inCamera” mode whenever I set view to camera. Also, I’d be glad if there is a way to use developer tools in camera mode as it isn’t very helpful that one cannot determine when runRenderingContext has switched to “inCamera”.

We’ll work to make the camera mode more debuggable as I can see why that would be a barrier when developing. In the meantime, you should be able to use the promise resolution in conjunction with zoomSdk.postMessage and zoomSdk.onMessage to pass information between instances of of the application.

We have documentation on this process here:

In-client Experience

and an example of how this can be done in the following repository:

zoom/zoomapps-customlayout-js/blob/9bc6a3df444f7fc71354fa9c0269682a48613039/public/js/index.js#L360-L369

@victoriaolanipekun

When i’m using the drawWebView and drawImage APIs, none of them seems to work, but while testing drawParticipant API, it works in Immersive mode so it is not clear why both drawWebView and drawImage wouldn’t work in camera mode, and these two are important in rendering the webview (the feature). This issue might also be because the camera mode is not being initiated as discussed in the first point.

I’m not sure why this wouldn’t be working. Once you have debugging set up via postMessage functions I expect that you can confirm if camera mode is initialized correctly.