Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ParticipantDevice missing #381

Closed
Iram1995 opened this issue Dec 4, 2024 · 6 comments
Closed

ParticipantDevice missing #381

Iram1995 opened this issue Dec 4, 2024 · 6 comments
Assignees
Labels
Bug This change resolves a defect
Milestone

Comments

@Iram1995
Copy link

Iram1995 commented Dec 4, 2024

Hi,

I hope you’re doing well.
I’m encountering an error while syncing participants from Zoom into my CRM. I’ve already obtained latest the version from ZoomNet, but the issue persists.
Could you please assist me with this?
Thanks,
Iram
image
image

@Jericho Jericho self-assigned this Dec 4, 2024
@Jericho Jericho added the Bug This change resolves a defect label Dec 4, 2024
@Jericho Jericho added this to the 0.85.0 milestone Dec 4, 2024
@Jericho
Copy link
Owner

Jericho commented Dec 4, 2024

Thanks for reporting.

Please note that this is an ongoing issue discussed in #369 that we escalated to Zoom for assistance. I encourage you to participate on the Zoom forum to let the Zoom person know that more and more people are affected by this problem.

The root of the problem is that the Zoom API behavior does not match their documentation. The documentation lists the valid values that can be returned from the API but the API intermittently returns values that are outside of these valid values. We asked Zoom to help us understand what's going on but so far no progress has been made. I don't know whether the behavior we are observing is a bug in their API or whether the documentation is simply incorrect and should be ignored. The Zoom person I have been communicating with hasn't been able to confirm one way of another so far.

I can publish a hot fix for your specific scenario which will ensure that Windows 10 is successfully parsed despite the fact that it is not a valid value, according to Zoom's documentation. But I want to be clear that you will face the same exception if/when the Zoom API returns another undocumented value.

@Jericho
Copy link
Owner

Jericho commented Dec 4, 2024

I told the Zoom person about the problem you are witnessing and they are asking for the following info:

I am really sorry for the delay here…
I just re engaged with our Engineering team but what i want to do next, is to create another ticket an assign it to a different team. I would just need the name of the app you are using to call the API and the email associated with it so I can use that data to report the issue… could you provide that data?

Can you provide the name of your Zoom OAuth app and the email associated with it?

@Jericho
Copy link
Owner

Jericho commented Dec 5, 2024

Nevermind, the requested info is no longer necessary.

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 "Windows 10".

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

But I will still publish an update shortly to overcome the current issue you raised.

@Jericho Jericho closed this as completed in 71373c3 Dec 5, 2024
@Iram1995
Copy link
Author

Iram1995 commented Dec 5, 2024

Thank you so much for quick fixes.

@Jericho
Copy link
Owner

Jericho commented Dec 5, 2024

Version 0.85.0 is being published as we speak and should be on NuGet.org within the next hour or so.

@Jericho
Copy link
Owner

Jericho commented Dec 5, 2024

🎉 This issue has been resolved in version 0.85.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This change resolves a defect
Projects
None yet
Development

No branches or pull requests

2 participants