SDK 1.8.5 - Zoom component try to reconnect after leaving a meeting instead of closing

[nvivot]

Description
When leaving a zoom meeting with a participant, the zoom frame detect this as a disconnection and try to reconnect instead of just closing like before.

This also has an impact on what is reported on Zoom meeting dashboard, such participant is then seen twice instead of once.

Which version?
1.8.5

To Reproduce(If applicable)
Just leave a meeting.

[nvivot]

@tommy

Has this problem been reported to developers already ?

[lfrancia]

Hi,

I tested this on Zoom sample app as well and confirmed that it is occurring there as well.

Before the host leaves the meeting

After the host left and rejoined the meeting

After host leaving and rejoining the meeting again

Tested it on web sdk v.1.8.5

Regards,
Lara

[tommy]

Hey @lfrancia, @nvivot,

Thanks for sharing this issue, we are aware of it and will be fixing it in the 1.8.6 release in early Jan. (CS-2714)

-Tommy

[tommy]

Hey @nvivot , @lfrancia ,

This should now be fixed. Please upgrade to version 1.8.6:

Web SDK update version 1.8.6

Hello Zoom Developers, here are the updates for the Web SDK version 1.8.6 release : Bug Fixes Fixed Attendee cannot join in to BreakOut Room when “Enable Waiting Room” is enabled. Fixed Attendee Leaves meeting show 'trying to reconnect’. Fixed Joined audio user can’t show waiting room when be put on hold. Fixed Android Chrome Audio don’t work. Fixed Audio stops working when High-Fidelity/Stereo Mode is Enabled. Fixed Start Video Black Screen in Mac When Only One attendee. Fixed “The host mute/…

Thanks,
Tommy

[Meks]

@tommy This is still an issue even after updating to @zoomus/websdk 1.8.6

[nvivot]

@Meks @tommy

We just upgraded to 1.8.6 for tests and we cannot reproduce it anymore. Looks like for us it fixed the issue.

[tommy]

Thanks for confirming @nvivot !

-Tommy

[tommy]

Hey @Meksm

If you are still seeing this issue in 1.8.6 can you please start a new topic and fill out the post template so we have enough details to debug?

Thanks,
Tommy

[Meks]

@tommy thanks had to check again, I can now confirm it is fixed.

[tommy]

Thanks for confirming @Meks !

-Tommy