ParticipantDevice Enum Missing Entry for 'Web Browser Chrome 129' from Zoom API

[TamasSzilagyi84]

Issue Summary:
When loading participants of an ongoing Zoom meeting using the NuGet package, an exception is thrown because the ParticipantDevice enum does not include a value corresponding to 'Web Browser Chrome 129'.

Steps to Reproduce:
Use the NuGet package to fetch participants from an active Zoom meeting.

Expected Behavior:
The ParticipantDevice enum should contain all possible device strings returned by the Zoom API.

Actual Behavior:
The absence of a matching enum value for 'Web Browser Chrome 129' results in an exception.

Additional Information:
The device string 'Web Browser Chrome 129' lacks a delimiter (if I remember correctly).
The issue was observed with a user running Chrome version 129.xxx.

[Jericho]

Is this the only "unknown" value you have observed? I will contact Zoom and ask them if it's normal for their API to return values that are not documented.

[Jericho]

I posted a question on the Zoom developer forum. Let's see what they say.

[Jericho]

@TamasSzilagyi84 A Zoom support person has posted a comment on my question. They are investigating and may come back requesting additional info. Please monitor the question and help provide the information since I will more than likely not be able to provide it.

[Jericho]

@TamasSzilagyi84 the Zoom person working on our case asked me the following:

Could you please share with me the account ID or email associated with the app that you are using to get this data so I can reach out to our Engineering team about it?

Is this something you can share?

[Jericho]

@cropter123 You and I worked on #354 a few months ago because you were receiving values in the device node that did not correspond to the documented possible values which caused ZoomNet to throw an exception when attempting to parse the JSON. You and I came up with a workaround but we never addressed the root of this issue: why is the Zoom API returning values that do not correspond to the documented values. I asked about this situation on Zoom's developer forum and a Zoom employee is looking into it. They asked me to share an account ID or email associated with the app to help them investigate.

Would be willing to share this information?

[cropter123]

Yes the account I used was: [email protected]

[Jericho]

Thank you. I'll relay this info to elisa.zoom and will keep you in the loop.

By the way, I encourage you to contribute to the Zoom forum question if you have additional info you whish to share regarding this situation

[Jericho]

eliza.zoom is asking the following:

I will just need the name of the app that made the API call as well as the email associated with that account in order to investigate this further

@cropter123 Can you provide the name of your app. Also, correct me if I'm wrong, the gmail.com email you previously provided is the email associated with the account right?

@TamasSzilagyi84 Any chance you could provide this information along with the ID of a meeting where you observed an attendee with an undocumented device?

[Jericho]

Guys, gentle reminder that eliza.zoom is waiting for the additional info. If you don't want to share this info with me for security reasons (which would be totally understandable), please contact Eliza directly on the Zoom developers forum (and let me know if you do so, so I don't bother you again in a few days).

[TamasSzilagyi84]

@Jericho Sorry for the late reply, but we have been quite busy lately.
So far, Web Browser Chrome 130 appears to be the only suspicious device name I could replicate. It seems that "130" represents the version, as it previously was "129".

As for the details, we are currently in the process of obtaining approval on what information we can share and with whom. Unfortunately, I will have to wait for this approval.

The endpoint we are calling is metrics/meetings/{meetingId}/participants

[Jericho]

Thanks for the update. Like I said, if you don't feel comfortable sharing sensitive info with me (which I totally understand) please reach out to Elisa directly. She's a Zoom employee. You can send her a private message on the Zoom developer forum.

[TamasSzilagyi84]

@Jericho I have just asked her to DM me so we can share the necessary information with her.

[Jericho]

It didn't occur to me that tamasss84 was you!!!! I thought it was some other developer reporting the same problem which is why I asked that person to publicly share info about what they are observing. Feel free to ignore my comment on the Zoom forum. In fact, I'll try to delete it.

[Jericho]

Good news: the Zoom team has acknowledged that there is an issue on their end and the device node is not intended to contain version information. It should contain values such as "Windows", not "win 10+ 17763".

we are currently working on reverting our logic back to only displayin the OS without the OS version
I am now waiting to hear back from the team to get an estimated timeline for this release

I asked for clarification regarding the scenario where a participant joined a meeting in a browser. My assumption is that device will contain a value similar to "Web Browser", os will contain the name of the browser such as "Chrome" or "Edge" for example, and os_version will contain the version of the browser.