This is a general issue, so all you need to do is create a call with Twilio Client.
Steps to reproduce:
Block requests to eventgw.twilio.com/v4/EndpointEvents in Chrome Network tab.
Start a call.
Observe that there is a large number of errors without any message in the console.
These errors are caused by requests failing to EndpointEvents endpoint.
Expected behavior:
There should be an error/warning logged with meaningful message. For example, when a request to EndpointMetrics fails, then the following warning is logged
This is probably how it should work for EndpointEvents as well.
Our application reports all uncaught errors which we later investigate and these errors create a lot of noise and are hard to filter out at the moment.
Actual behavior:
There are errors in console without a message.
Software versions:
Affects the latest Twilio Client version regardless of browser, operating system, 3rd party libraries.
Code to reproduce the issue:
This is a general issue, so all you need to do is create a call with Twilio Client.
Steps to reproduce:
eventgw.twilio.com/v4/EndpointEvents
in Chrome Network tab.These errors are caused by requests failing to EndpointEvents endpoint.
Expected behavior:
There should be an error/warning logged with meaningful message. For example, when a request to EndpointMetrics fails, then the following warning is logged
This is probably how it should work for EndpointEvents as well.
Our application reports all uncaught errors which we later investigate and these errors create a lot of noise and are hard to filter out at the moment.
Actual behavior:
There are errors in console without a message.
Software versions:
Affects the latest Twilio Client version regardless of browser, operating system, 3rd party libraries.