Polling options via Web SDK disabled?

Description
After downloading Web SDK version, launching it on the webserver and joining a meeting, user is not able to submit vote because the vote options are disabled

Error
No error

Which Web Client SDK version?
1.8.6

Screenshots

Device (please complete the following information):

  • Device: HP Desktop PC
  • OS: Windows 10
  • Browser: Chrome
  • Browser Version Versie 90.0.4430.85 (Officiële build) (64-bits)

In the vote dialig it’s mentionned ‘Host and participants can’t vote’
Is this because the participant is a guest and needs to be authenticated to be able to vote?

Or is there something else going wrong?

Thx
Frederik

Hey @frederik.gysel,

Thank you for reaching out to the Zoom Developer Forum. First, please test with the latest version of the Web SDK (1.9.1) and let me know if you see different behavior.

Thanks,
Max

Hi @MaxM ,

After upgrading to v1.9.1, participants are able to vote, thank you.

But… the vote registration is not done with the name & e-mail entered but as ‘guest’:

image

Is it possible to do the registration with the user name & e-mail entered on index.html page?

Thx
Frederik

Hey @frederik.gysel,

I’m glad that helped! Are you able to offer more information on how you’re generating that report? I’ll reproduce the issue and then reach out to our engineering team if necessary.

Thanks,
Max

Hi @MaxM,

Sorry for late reply…

Once poll is finished, I press the button ‘Download’ at the bottom of the poll dialog:
image

I just tried it once more for meeting ID 87636368225 and the report still contains ‘Guest’ in the field ‘User Name’:

As you can see in my first post, I am using Web Client SDK (version 1.9.1)

Thx
Frederik

@MaxM,

This looks like an old issue.

Please see:

and

Apparently fix for this was planned for Oct20?

When is the implementation of the fix foreseen?
Are there any alternatives to avoid ‘guest’ registration in polling?

Rgds
Frederik

Hey @frederik.gysel,

Thanks for providing more detail, that’s a good find. I’ve reached out to the engineers that handled that issue to see if they can confirm if the fix was deployed and if not, provide a timeline. (ZOOM-150127)

Thanks,
Max