Linux SDK gets stuck in MEETING_STATUS_CONNECTING when the provided password is incorrect

Meeting SDK Type and Version
Linux SDK Version v6.4.0.7800

Description
When using the linux SDK, if the bot attempts to join a meeting and the password it uses is incorrect, the bot gets stuck in the MEETING_STATUS_CONNECTING status. Instead I would expect it to get put in the MEETING_STATUS_FAILED status with a fail code of MEETING_FAIL_PASSWORD_ERR.

This issue can be reproduced using the sample program at GitHub - zoom/meetingsdk-linux-raw-recording-sample

Error?
This is the output when running sample program at GitHub - zoom/meetingsdk-linux-raw-recording-sample

Recording token is 
Leaving recording token as NULL
join_meeting:success
onLoginReturnWithReason: 0
onMeetingStatusChanged: 1, iResult: 0
Connect to the meeting server status.

The last line is written when the status changes to MEETING_STATUS_CONNECTING. After that, the status never changes and no more output is written.

Troubleshooting Routes
I was able to reproduce this on the sample app.

How To Reproduce

  1. Download and build the sample program at GitHub - zoom/meetingsdk-linux-raw-recording-sample
  2. Fill out config.txt with the correct meeting number and password
  3. Verify that the bot joins the meeting successfully
  4. Change the password in config.txt to be incorrect
  5. The bot will be stuck in the MEETING_STATUS_CONNECTING status.

@chunsiong.zoom @donte.zoom @elisa.zoom Making sure you guys see this. It’s super easy to reproduce because you can reproduce using the sample program.

@chunsiong.zoom @donte.zoom one more attempt to bump

Hi @noah.duncan
Sorry for the late reply here.
I will make sure we get back to you with some help!

Thanks @elisa.zoom looking forward to a response!