I tested the SDK behavior for invalid meeting password. I didn’t get MEETING_STATUS_FAILED with MEETING_FAIL_PASSWORD_ERR reason code. Instead, I saw the following status callback:
MEETING_STATUS_CONNECTING
MEETING_STATUS_DISCONNECTING
MEETING_STATUS_ENDED with reason 0
If I read correctly, you want to know how the zoom meeting password is invalid? The way that you can know is when you go into the zoom app, you put the correct Meeting Code. Zoom will then take you you the password. If you type it wrong, it will not let you enter the meeting because there is no meeting with that password.
Hope this help,
Gabe @PantherDeveloper
Hi @PantherDeveloper, I need a way to detect it programmatically from Zoom Windows SDK. I doesn’t look like the SDK calls IMeetingServiceEvent::onMeetingStatusChanged with the expected status code.
It’s the same behavior with or without ZAK. I also noticed a slight difference between the following two scenarios
provide empty password for meeting with password enabled:
We received “connecting”, “disconnecting” and “ended with reason 0” events within a 200~300 ms window.
provide incorrect password for meeting with password enabled:
We received only the “connecting” event. We didn’t receive the other two. The SDK seems to hang somewhere.