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

**URL:** <https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758>\
**Category:** Web\
**Created:** [April 1, 2025, 5:22am UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758 "2025-04-01T05:22:20Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [April 1, 2025, 5:22am UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/1 "2025-04-01T05:22:20Z")

</div>

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

```plaintext
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:

> **[init | Zoom Meeting SDK for Web](https://marketplacefront.zoom.us/sdk/meeting/web/functions/ZoomMtg.init.html)**
>
> Documentation for Zoom Meeting SDK for Web

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

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [April 1, 2025, 3:17pm UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/2 "2025-04-01T15:17:46Z")

</div>

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”

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [April 1, 2025, 11:48pm UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/3 "2025-04-01T23:48:59Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [April 28, 2025, 7:35am UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/4 "2025-04-28T07:35:02Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [May 19, 2025, 4:20am UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/5 "2025-05-19T04:20:12Z")

</div>

Still an issue in v3.13.2.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [May 19, 2025, 4:38pm UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/6 "2025-05-19T16:38:52Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [May 19, 2025, 11:59pm UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/7 "2025-05-19T23:59:15Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [May 20, 2025, 1:41pm UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/8 "2025-05-20T13:41:44Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [May 20, 2025, 7:15pm UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/9 "2025-05-20T19:15:12Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [May 21, 2025, 12:26am UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/10 "2025-05-21T00:26:29Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [July 17, 2025, 2:32pm UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/11 "2025-07-17T14:32:28Z")

</div>

Fixed in v4.0.0. Thanks for fixing.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [July 17, 2026, 2:32pm UTC](https://devforum.zoom.us/t/unexpected-console-warning-your-defaultview-is-not-supported-undefined/130758/12 "2026-07-17T14:32:29Z")

</div>

Closed on July 17, 2026, 2:32pm UTC

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
