Users unable to join Zoom Session

Description
@tommy @vic.yang Users are unable to join session in Video SDK, getting this error in console

And upon further checking its looks like one of the websocket connection is sending invalid JSON response:


(no closing double quotes)

This is the websocker URL → wss://zoommb13422414174rwg.cloud.zoom.us/instantsdk/94838336497?dn2=VmFpYmhhdiBTdXJhbmE&topic=YmJ4cGZ2Y3pmYnJyc3d3b2NhaHZ6ZnBmbGxmeWFkZHM&auth=k6cfttEHwFveG0bfla6pzt9mlyavkoHoEeDbcRx8Kic&browser=Chrome110&trackAuth=a0tgRU6tjb4oaBrAIlLXsH5Gz7kgK90oKdSABJo7Hc0&mid=OaxfJdEnSNCJ8PZEl2dPFw%3D%3D&tid=v%3D2.0%3Bclid%3Daw1%3Brid%3DWEB_6839182f7f7d25799fdf3364fb51af17&lang=en-US&ts=1676875641671&ZM-CID=7ec997bd-ff47-4217-afaf-a730e7e75036&_ZM_MTG_TRACK_ID=&iccv=1.4.1&customer_key=&cfs=0&zlkJwtToken=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBfa2V5IjoiUTlsa2RlYkxzSm53dnJ3bHRrWUtieTZCVEVLYUF4cDlMbGYxIiwicm9sZV90eXBlIjoxLCJpYXQiOjE2NzY4NzU1NzgsImV4cCI6MTY3Njg4Mjc3OCwidHBjIjoiYmJ4cGZ2Y3pmYnJyc3d3b2NhaHZ6ZnBmbGxmeWFkZHMifQ.Lm6VIDlaD9ktl4wyTBRM0a2qTw5tYgaPHYhauQ4yn3Y&rwcAuth=MTY3Njg3NTY0MTk1My4iK4Vs7SqoEn2YSjtupVgQkgX9r2JyRSo3YS7i30qQPQ&as_type=2

Is there someone else also who is facing the same issue?

Additional Context:
Video SDK version → 1.4.1

Hey @shoaib

Thanks for your feedback.

We will fix it asap.

Thanks
Vic

hey @vic.yang any ETA on this?

As we had to turn off Zoom SDK for all our customers.

Hey @shoaib

We will fix it within 3 hours.
I will let you know once it was fixed.

Thanks
Vic

Hey @shoaib

We have already fixed the issue and it is in the process of being deployed.

Thanks
Vic

1 Like

Thanks @vic.yang ,

Can you please share some sort of RCA of this issue?

Hi, It appears that the invalid JSON response being sent by the WebSocket connection is causing the issue with users being unable to join the session in Video SDK. This is likely due to a bug or issue with the WebSocket server on the Zoom side.

You can try reaching out to Zoom’s support team to report the issue and see if they can provide a fix or workaround. In the meantime, you could try using an older version of the Video SDK to see if the issue persists, or try using a different WebSocket server if possible. You could also try clearing the cache and cookies in your browser or using a different browser to see if that helps.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.