Repository navigation
not working with chrome? Cannot parse given Error object #198
Description
window.onerror = function (msg, file, line, col, error) {
StackTrace.fromError(error, line).then(callback).catch(errback);
}
var errback = function (err) {
console.log(err.message);
};
var callback = function (stackframes) {
var stringifiedStack = stackframes.map(function (sf) {
return sf.toString();
}).join('\n');
};
Cannot parse given Error object
adding,
window.onerror = function (msg, file, line, col, error) {
StackTrace.fromError(error, line).then(callback).catch(errback);
}
var errback = function (err) {
console.log(new Error("from onerror").stack);
};
var callback = function (stackframes) {
var stringifiedStack = stackframes.map(function (sf) {
return sf.toString();
}).join('\n');
};
Error: from onerror at errback (PatientRegistration:1590) at anonymous
Activity
ConClavi commentedon Sep 3, 2017
@eriwen, is this a new issue, I m using cdn lib
rgfactory commentedon Oct 18, 2017
This error occurs if you throw a string. You have to do
new Error("your string").ubershmekel commentedon Nov 15, 2017
@rgfactory an error may be in a 3rd party library, or a programmer made a mistake. A library designed to handle errors shouldn't break in the face of a common error.
1-0-1 commentedon Nov 15, 2017
Just started using this and I'm getting this error, too. I am getting it when passing back a Response from http in Angular 4.
ConClavi commentedon Dec 20, 2017
I am closing this. the dev totally ignored it. I moved to angular and this project does not stop throwing weird errors left and right.
capaj commentedon May 8, 2019
@embryologist how does closing the issue help?
ubershmekel commentedon May 8, 2019
@embryologist - I will open a separate issue if you keep this closed. Please re-open.
niftylettuce commentedon Dec 5, 2019
Re-opened. We will resolve this.
mmarekbb commentedon Mar 15, 2022
Has there been any progress on this issue? We now started getting it as well. This ticket has been open for almost 5 years.
zlawson-ut commentedon May 7, 2022
This error was being thrown for me due to passing a
StringorResponsetoStackTrace.fromError. It'd be good from developer experience perspective if StackTrace handled things like this or raised a helpful error.