# .join() Doesn't Throw Errors in Web SDK v1.12.14

**URL:** <https://devforum.zoom.us/t/join-doesnt-throw-errors-in-web-sdk-v1-12-14/122376>\
**Category:** Video SDK\
**Tags:** video-sdk\
**Created:** [December 12, 2024, 8:40pm UTC](https://devforum.zoom.us/t/join-doesnt-throw-errors-in-web-sdk-v1-12-14/122376 "2024-12-12T20:40:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![azimjs](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@azimjs](https://devforum.zoom.us/u/azimjs)\
**Post date:** [December 12, 2024, 8:40pm UTC](https://devforum.zoom.us/t/join-doesnt-throw-errors-in-web-sdk-v1-12-14/122376/1 "2024-12-12T20:40:27Z")

</div>

## Video SDK Type and Version

Zoom Video Web SDK v1.12.14

* * *

## Description

In Zoom Web SDK v1.12.14, the `.join()` method does not throw an error when provided with an invalid `topic` ID. Instead, it loads indefinitely and eventually times out. This behavior breaks error handling and complicates debugging.

* * *

## Error

No error is thrown in the `catch` block on passing an invalid `topicId`. Expected behavior is observed in `v1.12.5`, where the following error is thrown:

```json
{ 
  "type": "JOIN_MEETING_FAILED", 
  "reason": "Verify JWT failed", 
  "errorCode": 200 
}

```

* * *

## Troubleshooting Routes

1. Tested with different invalid topic IDs.
2. Verified behavior across multiple SDK versions:
  - `v1.12.5`: Errors are thrown as expected.
  - `v1.12.14`: No error is thrown; the SDK loads indefinitely.

* * *

## Quick Repro Steps

1. Use Zoom Video Web SDK v1.12.14.
2. Generate a valid JWT signature.
3. Call the `.join()` method with an **invalid `topic` ID** :

```auto
   await zmClient.join(topic + 'invalidId', signature, name, password).catch((e) => {
       console.error(e);
   });

```

1. Observe that no error is thrown, and the method loads indefinitely.
2. Downgrade to SDK v1.12.5, where the same call will throw the `JOIN_MEETING_FAILED` error

---

<div class="post-metadata">

**Author:** ![ekaansh.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ekaansh.zoom/32/55004_2.png) [@ekaansh.zoom](https://devforum.zoom.us/u/ekaansh.zoom)\
**Post date:** [December 13, 2024, 10:04am UTC](https://devforum.zoom.us/t/join-doesnt-throw-errors-in-web-sdk-v1-12-14/122376/2 "2024-12-13T10:04:39Z")

</div>

Hey @azimjs thanks for flagging this. I can reproduce. We’ll try to fix this in the next release.

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [December 20, 2024, 5:37am UTC](https://devforum.zoom.us/t/join-doesnt-throw-errors-in-web-sdk-v1-12-14/122376/3 "2024-12-20T05:37:22Z")

</div>

Hey @azimjs

We will fix it in the next release.

As a workaround, you can listen to the `connection-change` event. In the mentioned case, the event will be triggered with the payload:

```auto
 {state: "Fail",reason: "Verify JWT failed", errorCode: 200 }

```

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![ekaansh.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ekaansh.zoom/32/55004_2.png) [@ekaansh.zoom](https://devforum.zoom.us/u/ekaansh.zoom)\
**Post date:** [December 20, 2024, 2:44pm UTC](https://devforum.zoom.us/t/join-doesnt-throw-errors-in-web-sdk-v1-12-14/122376/4 "2024-12-20T14:44:55Z")

</div>

Closed on December 20, 2024, 2:44pm UTC