Angular5 Http error - Cannot parse given error object #202

Activity

1. Splaktar commented on Jan 23, 2018

   

   Splaktar

   on Jan 23, 2018

   More actions

   I am seeing this as well. Interested in the proper way to workaround this or handle it.
2. Splaktar commented on Jan 23, 2018

   

   Splaktar

   on Jan 23, 2018

   Last edited by Splaktar

   More actions

   For now, I'm just not sending these Errors to stacktrace.js:

       // Don't try to send stacktraces of HTTP errors as they are already logged on the server
       // and they cause stacktrace-js to throw an exception.
       if (!error.url && !error.headers) {
         // get the stack trace
         StackTrace.fromError(error).then(stackframes => {
         ...
         }
       }
   

   👍React with 👍7Reacted by Angelika Stigenberg, Kai, Matmo10, txavier, thatsmeta, Bhanu Kumar and Hicaro Adriano

   🎉React with 🎉1Reacted by Bhanu Kumar
3. JoeScylla commented on Sep 19, 2018

   

   JoeScylla

   on Sep 19, 2018

   More actions

   With ExtJS i had the same problem.

   This should be because in chrome user defined exceptions dont have a stacktrace by default. As there is nothing to parse stacktrace.js throws an error. To get a stacktrace in user definedexceptions you have to use the V8 STacktrace API; see: Error.captureStackTrace().

   Example with standard javascript:

   function MyError(message) {
   	this.message = message;
   	
   	if (Error.captureStackTrace) {
   		Error.captureStackTrace(this, CustomError);
   	} else {
   		this.stack = (new Error).stack;
   	}
   }
   MyError.prototype = Object.create(Error.prototype);
   MyError.prototype.name = "MyError";
   

   For ExtJS i just overwritten the constructor of the default exception.
4. johannesjo commented on Jan 10, 2020

   

   johannesjo

   on Jan 10, 2020

   More actions

   @JoeScylla not sure about this, but according to this new Error().stack should be always undefined for a couple of browsers.