Description
Hello! I’m currently experiencing the exact same problem seen here:
I also understand that the solution is here:
But my problem is I am unsure where to place the code snippet posted by mtaha relative to the code that gets the authentication result, assuming my code follows the same general format as the code seen in link #1, and that everything is located in main() at the moment.
I think this also falls down to me not exactly understanding the solution, and I apologize in advance for my inexperience, but I’d really appreciate some help or perspective on this one
Which Windows Client SDK version?
I am working in zoom-sdk-windows-5.5.12511.0422.
Device (please complete the following information):
I found the images on this documentation page somewhat useful. On those flow images, any point where the arrows are dotted and pointing to the left your application should be essentially just waiting for a callback. This is when the message passing is essential for the application to function, as otherwise those callbacks will never be called.
In your case, calling the message passing loop after calling SDKAuth should let you authorize successfully, provided you have given the SDK a callback. The simplest way to make this work is:
Initialize the SDK by calling InitSDK with valid params
Get an authService by calling CreateAuthService
Give it your event handler (which is a class that extends IAuthServiceEvent) by calling the authService’s SetEvent function
Call the authService’s SDKAuth (with a valid JWT)
Spin in the message passing loop until the callback has been called (your callback could break the loop somehow once it’s successfully called)
A similar order of events happen for other parts of the SDK as well (e.g. logging into a Zoom account), so I used a sort of state machine where my application had active states where it would perform actions (e.g. sending out auth or login requests) and passive states where it would simply allow the message loop to continue because it had to wait for a callback (e.g. when waiting for auth or login).
Hopefully this description is enough to at least get you a successful auth; things made a lot more sense for me once I finally figured out this problem.
Put this code at the end of your main function before return.
unsigned int bRet = -1;
MSG msg;
while ((bRet = GetMessage(&msg, nullptr, 0, 0)) != 0)
{
if (bRet == -1)
{
// handle the error and possibly exit
}
else
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
}
This is incredibly useful advice! I am beginning to understand, thank you both very much. I will get to working on the suggestions you’ve given to me and see if everything works fine.
It’s a little embarassing to say, but I completely glossed over the fact that I hadn’t even implemented any functionalities to the class I made that derived IAuthServiceEvent. I appreciate the help, thanks very much!
Hello again! I got the Zoom SDK to join a meeting without many hiccups thanks to your advice.
It all really boiled down to me being unfamiliar with the Windows API overall, I didn’t understand at first what the message loop was for, and thought I’d have to put function calls in the loop somewhere and expect it to fire when appropriate.
