On version v4.6.15801.0403 of the SDK and using a custom UI.
Users can join meetings using a meeting number and that works fine regardless if they are logged in or not.
However, if the user joins via a meeting URL, MeetingService.handZoomWebUrl(), the behavior is different depending on if they are logged in. If logged in, everything works fine. If they are not logged in, the MeetingService will transition from IDLE to CONNECTING and then just stay in that state. If the host has not started the meeting, the MeetingService will transition to WAITINGFORHOST. When the host finally starts the meeting, the MeetingService just stays in WAITINGFORHOST.
I tried a meeting with no password, a meeting with a password and a meeting with an embedded password in the URL. Same result. Although, when you try to join via a URL and the password is not embedded in the URL, the SDK is properly notifying that a password is required. But after entering the password, the MeetingService remains in a CONNECTING state.
For now I’ve worked around this by requiring users to be logged in before they can use this feature. But it is not ideal and this seems like a bug with the SDK.