ONCLOSE resetWebclient Error in Zoom Web SDK: Meeting Restarts After Joining

Meeting SDK Web
1

Hello Zoom team and community,

I’m experiencing a very specific issue with the Zoom Web SDK integration in my Angular application. The problem is that the meeting “restarts” right after the user has been successfully admitted and joined.

Problem Description

A user enters the meeting, the “waiting for host” screen disappears, and the Zoom client initializes. However, instead of remaining in the meeting, the web client abruptly closes and restarts, returning to a loading screen. This behavior is intermittent and only occurs with a subset of our users.

This seems to be a low-level SDK issue, as it is consistently reproducible even when testing with the official Angular implementation from Zoom’s own repositories. The problem also persists when using the official Node.js code to generate the signature, ruling out a backend issue with the signature generation logic.

We have been able to capture the following critical logs in the browser console just before and during the restart:


ONCLOSE Reconnect websocket start to resetWebclient
>>> >>>>>>> resetWebclient >>>>>>>>>>>>>
destroy SDK

These logs suggest that the Zoom SDK itself, upon detecting an instability, internally decides to force a restart of the web client.

Environment and Version

  • Zoom SDK: Web SDK v4.0.0

  • Framework: Angular (using ngZone.runOutsideAngular for the SDK)

  • Browser: Chrome (latest version)

  • OS: macOS

  • Authentication Flow: We use a backend to generate the signature, which is sent to the frontend for ZoomMtg.join().

Debugging Steps Taken:

  1. We have validated the parameters passed to ZoomMtg.join(): meetingNumber is a number, userName and passWord are valid and non-empty strings.

  2. We have verified that the signature generated by our backend is valid and does not expire prematurely.

  3. We have tested in incognito mode and on multiple networks to rule out cache and local network/proxy issues.

  4. CRUCIAL: We have tested this behavior with the official Zoom Angular and React repositories, and the onCLOSE error persists even with those implementations when the user is accepted into the meeting. This rules out an error in our custom client-side code.

Specific Questions for the Zoom Team

  1. Under what internal conditions does the Zoom SDK call the resetWebclient and destroy SDK functions? Is it always a result of a non-standard WebSocket closure?

  2. Could an unexpected ONCLOSE be caused by an invalid or expired signature that the SDK does not detect in the join() phase but is only revealed during a later validation?

  3. Is the following warning that appears in the console normal?

    image
    image1802×1264 372 KB

    Add screemshot

  4. Is it possible that there is a misconfiguration in our main Zoom account settings that could be causing this specific onCLOSE error to occur?

We appreciate in advance any clues or information you can provide to help us resolve this critical stability issue.

1 Like
2

I had the same question!