-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Script error: Browser exception message not providing information type and method #363
Comments
Do you have pictures/examples of what and when should be collected? |
Most common undefined JS errors:
|
Script error with an "unknown" error message is reported by CORS scripts, this can be mitigated by adding Edit: I fixed a bug to unify all "Script error" messages. The SDK also will provide more info on how to fix this #424. |
See our Wiki page for more info: I'm seeing a lot of Uncaught [object Object] errors in Application Insights in Azure Portal |
Is there a way to override this behavior? Maybe specify an unknownErrorFormatter = function(error) { return formattedErrorToLog; } or something? Or is there another work around that is available? Currently, every single error logged is useless for us as it just says [object Something] and has no details what-so-ever about the error. |
The label "waiting for backend fix" as added to the wrong issue -- doh! |
As part of adding additional support to handle more error types, including the throwing strings and some older browsers. I'm also adding the ExceptionType to the beginning of the message (if it is not already present). As The exceptions to this will be if the ErrorType is
|
v2.6.3 is now fully deployed |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
No description provided.
The text was updated successfully, but these errors were encountered: