Your code looks alright to me, however I am curious if @bm.erikstad’s code resolves your issue. Can you try that and let us know so we can investigate further?
I have resolved this issue. it seems that there were some missing Dlls that were nto beign copied over to the bin folder.
Once I copied all the dlls from the bin folder in the sdk demo to my app folder, included them in my project and then marked them as copy to out put on build, meeting join started to work again.
I’m not sure if this is the correct fix, to be perfectly honest. But it seems to work. If missing dlls was the issue, is there any chance we could get a nuget package to make file management easier?
Thanks for all of the info you have provided in this thread I am assisting another developer who is running into this same issue so I was wondering if I could ask you some questions.
Do you know which DLL’s were causing issues?
What is your Windows OS version, and Visual Studio runtime library version?
Hello there,
I have installed zoom meeting software but I am getting the error XmppDll.dll file is missing from your computer. I have tried to reinstall it many times but the problem still exists. How can I get rid of this error?
Thanks.
This problem has recently re-appeared for me when logged as a Business level account and starting my meeting. The same issue appears when just trying to join a meeting being hosted by a Business account.
But works when using a basic level account and joining a meeting hosted by a basic level account.
The app is not yet published in the market place. Would this cause the issue?
It seems unlikely that it is the same issue if it’s only happening for certain account types. Is it possible that there is something enabled in the meeting settings (e.g. registration required) which is only applicable to the business account?
After debugging, I’m seeing MEETING_FAIL_CLIENT_INCOMPATIBLE. I’ve upgraded to the latest SDK.
So it appears that the Require Users to update the client is checked on the accounts where the issue is appearing.
There are two options
The first is asking the users to ask thier admins to uncheck, or lower the allowed client version. This is impractical.
The second is that the SDK gets updated in tandem with the Zoom client releases. I think ive read on other posts that this is something that is being considered internally.
I can make people aware of option 1, but i think this really does need to be resolved by zoom.
Unless the cadence picks up, there is a possibility that the SDK becomes unusable for the section of users who are forced by host and org account settings to have to have the latest client version when they connect to a meeting. This setting also applies to users who are external to the account. So the users affected grows quite a lot.
Thank you for the response. We agree with everything you said. The current state of this leaves gaps of time where the latest SDK is unusable, which is not acceptable. We are considering many different options to resolve this internally. We will let you know when we have updates about this.