Unexpected console warning "your defaultView is not supported: undefined"

Meeting SDK Web
1

The Zoom Meeting SDK for Web version 3.12.0 is logging an unexpected warning in the console when joining a webinar.

your defaultView is not supported: undefined, zoomus-websdk-zoommtgMain.umd.min.js:2

This did not occur in the previous version 3.11.2.

undefined should be a valid value for the defaultView init property as per the documentation:

Optional defaultView?: “gallery” | “speaker” | “multiSpeaker”
Sets the default video layout for the session. Optional.

2 Likes
2

Hi Chris,

Could you clarify how you’re currently handling the defaultView parameter in your implementation?

Are you explicitly passing a value for defaultView that might be undefined, or are you omitting the defaultView parameter entirely in your initialization?

This seems like it might be a change in how the SDK handles undefined values between versions. Version 3.11.2 might have silently accepted undefined, while 3.12.0 is more strict and produces a warning.

If you’re explicitly including defaultView in your initialization object, I’d recommend either:

  1. Removing the defaultView parameter completely, or
  2. Setting it to one of the valid values: “gallery”, “speaker”, or “multiSpeaker”
1 Like
3

Hi Amanda,

Thanks for your response.

I’m omitting the defaultView init parameter entirely and it’s logging the “your defaultView is not supported: undefined” warning.

I tried explicitly setting defaultView: "speaker" and it then logs a warning like “your defaultView is not supported: speaker”, which is very strange.

Interestingly, I then tried defaultView: "gallery" and no warning is logged.

In all cases the joining of the webinar seems to proceed successfully.

To me this clearly seems like a bug introduced in v3.12.0 and its usage should align with the SDK documentation.

4

FYI, this is still an issue in v3.13.1.

5

Still an issue in v3.13.2.

6

Hey @chris-praxhub
Thanks for reporting this issue.
I will troubleshoot this on my end and will share my findings with the Engineering team.
Are you using client or component view?

1 Like
7

Thanks for your response @elisa.zoom. I’m using the client view. Looking forward to getting this resolved.

8

Thanks for your patience @chris-praxhub
I am able to replicate this issue when passing the value “speaker” as well..
I will report this to our Engineering team and will get back to you soon

2 Likes
9

Hey @chris-praxhub
Just heard back from our Team and the default value for defaultView is “speaker” so yo do not need to set it. We will fix the docs to make it clear

1 Like
10

Thanks for following up on this @elisa.zoom.

The key issue I’m raising is the logging of unexpected/incorrect warnings in the console. Will this be fixed?

11

Fixed in v4.0.0. Thanks for fixing.

2 Likes