@twilio/conversations JS SDK Client unhandled rejection with expired token

edited June 7 in Conversations

Pulled from: https://stackoverflow.com/questions/64552855/twilio-conversations-js-sdk-client-unhandled-rejection-with-expired-token

In the JS SDK @twilio/conversations v1.1.0, when you try to create a Client instance with an expired token (i.e. ConversationsClient.create('expired token')), it will first throw an Exception which can be handled in the promise. However, after that it will throw more Exceptions that are not part of that promise, so they are not caught and cause an Unhandled Rejection.

I know that we should not be using expired tokens to begin with, but it would be nice for the website not to crash without potentially adding a unhandledrejection event to the window.




Sign In or Register to comment.