Questions Regarding Upgrade VideoSDK to Versions 2.1.10 and 2.2.0

Description

We are implementing upgrade VideoSDK from 2.1.0 to 2.2.0 but we confusing about this changelog:

  1. https://developers.zoom.us/changelog/video-sdk/web/2.1.10#enhanced

Improved exception handling in method returns by adding the errorCode property to identify exception types. We recommend that developers handle exceptions based on the new errorCode field to enhance error recognition accuracy and maintainability.

What errorCode values are available, and where can we find the list to determine whether we need to handle them?

  1. https://developers.zoom.us/changelog/video-sdk/web/2.1.10#fixed

Issue with canvas remaining black when video was stopped on Safari or Firefox without SharedArrayBuffer enabled.

Does this issue affect users on Edge or Chrome as well?

  1. https://developers.zoom.us/changelog/video-sdk/web/2.2.0/#added
  • isLogDetailed option to client.init method. The default is true, which sends detailed telemetry to Zoom when the session ends or the user leaves the session. If false, the baseline telemetry is sent to Zoom.

Will our existing manual reporting logs using clientSideTelemetry.reportToGlobalTracing() still function properly?
If we are already using clientSideTelemetry.reportToGlobalTracing and upgrade to 2.2.0 without changing anything, will that cause any issues?

  1. https://developers.zoom.us/changelog/video-sdk/web/2.2.0/#fixed
  • Issue with remote video on Chrome 137.

Can you tell us what issue occurred with Chrome 137? How can we reproduce this bug in the older version?

Which Web Video SDK version?
3.1.10, 2.2.0

Hey @leo_tristan

Thanks for your feedback.

What errorCode values are available, and where can we find the list to determine whether we need to handle them?

Does this issue affect users on Edge or Chrome as well?

No

Will our existing manual reporting logs using clientSideTelemetry.reportToGlobalTracing() still function properly?

Yes. It still works.

If we are already using clientSideTelemetry.reportToGlobalTracing and upgrade to 2.2.0 without changing anything, will that cause any issues?

No issues. No changes to your code are necessary.

Can you tell us what issue occurred with Chrome 137? How can we reproduce this bug in the older version?

Our extension of the VideoFrame API conflicts with the changes introduced in Chrome 137, which can cause rendering failures when remote video frames have rotation metadata. This issue only occurs on certain devices.

Thanks
Vic

2 Likes

@vic.yang Could I ask one more question?

We’re aware of these errors, but we’re unsure of the best practices for handling each one. Is there any documentation or guidance available that suggests how to handle each specific case?

https://developers.zoom.us/docs/video-sdk/web/error-codes/

Moreover, when an error message is vague—such as Occurs in client.init...—it’s unclear which specific function is causing the error. How should we handle these kinds of errors?

1 - OPERATION_TIMEOUT
2 - INTERNAL_ERROR

200 - SESSION_FETCH_INFO_ERROR - Session creation or retrieval error. Usually caused by an incorrect field value in the JWT token.
connection error
The token has expired, is over 2 days old, or is ineffective
Password max of 10 characters
This account does not exist or does not belong to you
Verify JWT failed
invalid session key
3004 - SESSION_INCORRECT_PASSCODE - The session passcode is incorrect.
3009 - SESSION_USER_REMOVED - The user was removed by the session host and is prevented from rejoining the same session.
3010 - SESSION_ROLE_TYPE_ERROR - Incorrect role type in the JWT token.
4003 - SESSION_INVALID_PARAMETER - Incorrect parameters for connecting to the Zoom server. If you encounter this issue, please report it to Zoom.
4004 - SESSION_ENDED - The session has ended.
5002 - CLIENT_SESSION_STATE_CLOSED - Called a function that requires the user to be in a session, but the session is closed.
5003 - CLIENT_SESSION_STATE_RECONNECTING - Called a function that requires the user to be in a session, but the session is reconnecting.
5006 - CLIENT_HOST_OR_MANAGER_PERMISSION_REQUIRED - Operation requires host or manager permission.
5007 - CLIENT_HOST_PERMISSION_REQUIRED - Operation requires host permission.
5008 - CLIENT_ORIGIN_HOST_PERMISSION_REQUIRED - Operation requires origin host permission.
5011 - CLIENT_MISMATCH_USER - User ID doesn't match.
6000 - STREAM_MISMATCH_DEVICE - The device ID (microphone, audio speaker, camera) does not match any device in the list.
6001 - STREAM_MISMATCH_USER - The User ID doesn't match.
6003 - STREAM_MISMATCH_RENDER_ELEMENT - Occurs in video or sharing-related functions when the target element does not match the required render element type.

Thank you for your time and support.

1 Like

Hi @leo_tristan

Video SDK - web - Error codes and troubleshooting

Error codes specifically refer to exceptions thrown when a method call encounters an issue.

Since different methods can fail in different ways, each has its own set of error codes. The error message typically includes context like ‘Occurs in client.init…’ to indicate which method the error is related to. You can refer to the latter part of the message—it often explains the scenario that triggered the error.

Based on that, you can provide guidance or avoid calling the method in such a way during development.

Thanks
Vic

2 Likes