When App Auto-Starts, it does not detect meeting context

When I have already loaded my app in the out-of-meeting Zoom panel UI, and then start a meeting, when the app auto-starts, it still shows the out-of-meeting UI.

Here are the scenarios:

  • Open the app in Zoom client out-of-meeting panel: Correct UI
    • Subsequently start meeting (auto-start app OFF). Manually open app in Zoom client in-meeting: Correct UI
  • Do not open app in out-of-meeting panel.
    • Subsequently start meeting (auto-start app ON). App starts: Correct UI
  • Open the app in Zoom client out-of-meeting panel: Correct UI
    • Subsequently start meeting (auto-start app ON). App starts: Incorrect UI

So the Zoom Apps SDK is sending its context header when you (a) open the app in the Zoom client out-of-meeting panel, (b) manually open the app in the Zoom client in-meeting, or (c) auto-start the app in a meeting only if this is the first time the app has loaded.

It does not seem that the context header is sent on app auto-start (in meeting), if the app has already loaded.

Attempts to solve:

  • I have tried to set up a server-side event that listens for rtms_started, notifies my UI, and hits getRunningContext – this has not worked so far.

Am I missing something?

Thank you.

@John6, Thanks for posting in the Zoom Developer Forum!

I’m not completely following the behavior you’re trying to achieve. Could you help us understand better? Are you saying that when the app hasn’t been loaded yet and you open it, the context header is sent on app auto-start? But you’re not seeing this happen when the app is already loaded?