From cf84dc5fb02ac9f7ec589db76615f5be73fb9151 Mon Sep 17 00:00:00 2001 From: Karthikeyan Date: Tue, 3 Jan 2017 15:18:30 +0530 Subject: [PATCH] Handling "Unhandled" Error message formats. Currently if we have any non formatted error message such as without having exception.name , exception.message , exception.stack. We are not tracking the error message instead we end up throwing exception for the track message. So, changed the code in a way that if any unhandled error message ( un-formatted ) we are handling in a app inshights code block. --- dist/angular-applicationinsights.js | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/dist/angular-applicationinsights.js b/dist/angular-applicationinsights.js index f9f4dc7..7947e84 100644 --- a/dist/angular-applicationinsights.js +++ b/dist/angular-applicationinsights.js @@ -852,9 +852,9 @@ var ApplicationInsights = (function () { handledAt: "Unhandled", exceptions: [ { - typeName: exception.name, - message: exception.message, - stack: exception.stack, + typeName: exception.name || "Unhandled", + message: exception.message || "Unhandled", + stack: exception.stack || "Unhandled", parsedStack: parsedStack, hasFullStack: !Tools.isNullOrUndefined(parsedStack) } @@ -978,4 +978,4 @@ var AppInsightsProvider = (function () { }; // invoked when the provider is run return AppInsightsProvider; }()); -//# sourceMappingURL=angular-applicationinsights.js.map \ No newline at end of file +//# sourceMappingURL=angular-applicationinsights.js.map