Browser API not showing requests

Zoom WebSDK does not show requests to unmute or turn on video on the participant’s UI. This occurs when the host sends a request to a participant joining through a browser.

Browser Console Error
No specific error message is observed.

Which Web Meeting SDK version?

Meeting SDK Code Snippets


import axios from "axios";
import ZoomMtgEmbedded from "@zoomus/websdk/embedded";

export default {
  name: "ZoomInterview",

  data() {
    return {
      client: ZoomMtgEmbedded.createClient(),

      sdkKey: "",
      meetingNumber: "",
      passWord: "",
      role: 0,
      userEmail: "",
      userName: "Unknown",
      signature: "",
      width: 0,
      height: 0,
  methods: {
    getCookie(name) {
      let cookieValue = null;
      if (document.cookie && document.cookie !== "") {
        const cookies = document.cookie.split(";");
        for (let i = 0; i < cookies.length; i++) {
          const cookie = cookies[i].trim();
          // Does this cookie string begin with the name we want?
          if (cookie.substring(0, name.length + 1) === name + "=") {
            cookieValue = decodeURIComponent(cookie.substring(name.length + 1));
      return cookieValue;
    startMeeting(signature) {
      let meetingSDKElement = document.getElementById("meetingSDKElement");
      let render__wrapper = document.getElementById("render__wrapper");
      let ref_block = document.getElementById("ref_block_for_sdkvideo");
      let enter_button = document.getElementById("meetingStartButton"); = "block";
      enter_button.disabled = true;
        zoomAppRoot: meetingSDKElement,
        language: "jp-JP",
        maximumVideoInGalleryView: 2,
        customize: {
          meetingInfo: [
          toolbar: {},
          video: {
            popper: {
              placement: "top left",
            isResizeble: true,
            viewSizes: {
              default: {
                width: render__wrapper.clientWidth,
                height: (ref_block.clientWidth / 16) * 9,
              ribbon: {
                width: render__wrapper.clientWidth,
                height: (ref_block.clientWidth / 16) * 9,
        sdkKey: this.sdkKey,
        signature: this.signature,
        meetingNumber: this.meetingNumber,
        password: this.passWord,
        userName: this.userName,
        userEmail: this.userEmail,
      this.client.on("connection-change", (payload) => { = "none";
        if (payload.state === "Closed") {
          console.log("meeting ended");
  mounted() {
    this.width =
    this.height =
  created() {
    let info = JSON.parse(document.getElementById("meeting_info").textContent);
    this.sdkKey = info.sdkKey;
    this.meetingNumber = info.meetingNumber;
    this.passWord = info.password;
    this.role = info.role;
    this.userEmail = "";
    this.userName = info.userName;
    this.signature = info.signature;

<style scoped></style>

To Reproduce

  1. Host sends a request to unmute or turn on video.
  2. Participant, joining through a browser-based WebSDK client (vue 2.0 js framework), does not see the request on their UI.


Troubleshooting Routes

  • Verified that the issue persists across different browsers and devices.
  • Checked for any relevant errors or warnings in the browser console.


  • Devices: Various (including iPhones and Android devices)
  • OS: Various
  • Browsers: Chrome, Safari (on iPhone)
  • Browser Versions: [Specify versions if known]

Additional Context
The issue seems to be consistent across different devices and browsers, impacting the user experience in Zoom meetings where participants are unable to see the host’s requests to unmute or turn on the video.

Hi @d.miyazaki
Thanks for reaching out to us!
Have you been able to troubleshoot this issue on your end or are you sill experiencing this behavior?
Could you please confirm if you can replicate this issue with our sample app?

Thank you @elisa.zoom for your response.
I tested with the sample-web and the issue didnt happen on this sample file. I still have no clue how to fix it, so any suggestions would be greatly appreciated.

Interesting, @d.miyazaki
Could you try and add your logic to the sample app to see if it triggers the same error?

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