# Websocket stuck in meeting connecting when joining via SDK

**URL:** <https://devforum.zoom.us/t/websocket-stuck-in-meeting-connecting-when-joining-via-sdk/135590>\
**Category:** Meeting SDK\
**Created:** [July 23, 2025, 2:14pm UTC](https://devforum.zoom.us/t/websocket-stuck-in-meeting-connecting-when-joining-via-sdk/135590 "2025-07-23T14:14:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryan6](https://avatars.discourse-cdn.com/v4/letter/r/c77e96/32.png) [@ryan6](https://devforum.zoom.us/u/ryan6)\
**Post date:** [July 23, 2025, 2:14pm UTC](https://devforum.zoom.us/t/websocket-stuck-in-meeting-connecting-when-joining-via-sdk/135590/1 "2025-07-23T14:14:59Z")

</div>

We have a problem with joining the zoom meeting using SDK and our Marketplace application but not when using Zoom Native app.

When the users are joining the meeting via Zoom SDK, the web socket is just stuck in “meeting connecting” and doesn’t succeed to “meeting connected”. We are able to replicate it in a specific primary zoom account but not in another primary zoom account. We tested this in various locations (South Africa, Philippines) and in two platforms (Web SDK, Android SDK). What could possibly be the issue for this?

---

<div class="post-metadata">

**Author:** ![Craig](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/craig/32/69695_2.png) [@Craig](https://devforum.zoom.us/u/Craig)\
**Post date:** [July 23, 2025, 3:31pm UTC](https://devforum.zoom.us/t/websocket-stuck-in-meeting-connecting-when-joining-via-sdk/135590/2 "2025-07-23T15:31:22Z")

</div>

Could just be the SDK app isn’t published. Zoom’s now blocking joins from unpublished ones.

---

<div class="post-metadata">

**Author:** ![ryan6](https://avatars.discourse-cdn.com/v4/letter/r/c77e96/32.png) [@ryan6](https://devforum.zoom.us/u/ryan6)\
**Post date:** [July 24, 2025, 12:39pm UTC](https://devforum.zoom.us/t/websocket-stuck-in-meeting-connecting-when-joining-via-sdk/135590/3 "2025-07-24T12:39:56Z")

</div>

Thank you for the reply.

I double checked, our app (General App) is published and the SDK keys used are correct. Usually when the SDK key is incorrect, there’s an explicit error we see before that indicates it.
