Closed PhilippSoehnlein closed 8 years ago
Thanks for the sample, I'll take a look into this.
Hey, I'm really sorry I haven't taken a look at this sooner. I'm currently looking into this.
This behavior is by design. Only the default client instance wires up to the environment specific error handlers as shown here (https://github.com/exceptionless/Exceptionless.JavaScript/blob/master/src/exceptionless.ts) for browsers. When you new up your own instance of the exceptionless client, you are responsible for wiring up to these handlers. The question should be: do we add a register or startup method that we call so you can hook up multiple clients to these error handlers.
To get them to log just set the api key on the default instance exceptionless.ExceptionlessClient.default
or part of the query string exceptionless.js?apiKey=YOUR_API_KEY
. Once you do this everything will be picked up:
Please let me know if you need any help or have any questions.
The Readme claims:
For me it looks like this isn't the case. Here's a reduced test case in which I would expect to get three exceptions logged to the server, which doesn't happen:
I tested with Firefox 46, Chrome 50 and Safari 9.1 on Mac OS 10.11.4.