Closed lukeapage closed 7 months ago
Hello @lukeapage,
Thank you for reporting this.
Filed internally as 204871
Thank you, Ryan
We are also seeing a bunch of these uncaught network errors reported to our Sentry (React Client SDK). A fix would be greatly appreciated!
Hi,
any plan to fix this @kinyoklion ?
We just released 3.1.4 which should fix this issue. Thank you for your patience.
Tested it. It is solved for me. I believe this issue should be closed.
Describe the bug We get unhandled exceptions in production that originate from the launch darkly sdk.
We aim to eliminate unhandled exceptions and fix any occurring in our own code, so having them reported from libraries leads to false positives that are hard to filter out.
I believe its simple - there is a synchnonous xhr and because it is synchronous it can throw if there is a network error and you don't have a try catch around it to handle the issue.
Related: https://github.com/launchdarkly/js-client-sdk/issues/147 Related: https://github.com/launchdarkly/react-client-sdk/issues/106 (I think this is more likely the cause of 106 than 147)
Stack Trace
Expected behavior Please catch the error and handle it. Feel free to emit a error event etc.
SDK version 3.1.2