Junk email of host when starting meeting through browser redirect

Meeting SDK Windows
1

Description
We are using Zoom Windows C++ sdk to create a zoom client which is being used to join a Zoom meeting. So, when a host is signed into the browser, but not in the OS application (have tested on Mac), and the host starts the meeting by clicking the zoom meeting url of the form https://zoom.us/j/<personal-meeting-id>, the browser opens the url which subsequently opens the zoom application and meeting is started. However, in such case the ZOOM SDK IMeetingParticipantsController returns IUserInfo object for host with junk email like “FmN4MpbkTai3f4SZGe4LFQ” instead of host’s email. Because of this issue, we are unable to identify the user in our system.

Which version?
v4.3.0.30730.0118

To Reproduce(If applicable)
Steps to reproduce the behavior:

  1. Sign out of Zoom Application in your OS (Mac)
  2. Sign in to zoom.us in browser.
  3. Click on your personal meeting url (https://zoom.us/j/<personal-meeting-url>)
  4. Browser opens the url which subsequently opens zoom application and meeting is started.
  5. Now, join the meeting using a ZOOM Windows C++ SDK.
  6. Print email of the participants by calling GetUserByUserID.
  7. Host’s Email is incorrect.

Screenshots
Please find below the screenshots taken when running the program in debug mode and stopping the execution on callback of OnUserJoin

Zoom%20Issue%202
Zoom Issue 2.png951×98 9.29 KB
Zoom%20Issue%201
Zoom Issue 1.png1010×356 31.2 KB

2

Hi Rishi,

Thanks for using Zoom SDK and thank you very much for providing the details. We will look into this issue and perform an investigation on this. I will get back to you as soon as I have any updates.

Thanks!

3

Hi Rishi,

Thank you very much again for this post and the details. We have looked into this issue and we have identified a bug that is related to this. We are working on fixing the bug and we are expecting this issue will be resolved in our next release. Pardon the inconvenience caused by this issue. Please follow our Github repo for any updates.

Thanks!

4

Thank You Very much for the prompt response.