Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
If `stacktrace` has not the standard format error won't show up in dashboard
See original GitHub issueWhile using window.fetch and Bugsnag.enableNotifyUnhandledRejections when an error occurs, somehow the stacktrace gets lost causing bugsnag.js to send stacktrace:TypeError: Failed to fetch to bugsnag’s servers, which in turn makes the error non-visible on the dashboard.
I suspect this has to do with the expected format for stacktrace
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Improve test error messages of your abstractions
That's a pretty standard stack trace for that error. The message is clear-ish, but we can do better and we do! If we...
Read more >Stack trace logging - Unity - Manual
Stack trace logging. Unity Console messages and log files can include detailed stack trace information. The console also links to the line of...
Read more >How to Log Full Stack Trace with Winston 3?
Yes, a console.dir of the info object does not show any meta. It instead shows some splat symbols. The internals must have changed....
Read more >A Definitive Guide to Handling Errors in JavaScript - Kinsta
Getting tripped up by errors in your JavaScript? We'll show you how to tame those errors so you can get back to developing...
Read more >Stack trace - Wikipedia
Memory is continuously allocated on a stack but not on a heap, thus reflective of their names. Stack also refers to a programming...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Wondering if this was ever solved, some 5 years later.
As @jmshal explained, async stack traces are not a “solved” problem in JS at the time of writing. We await a time when we can hook into them, but for now I’m closing this as it isn’t a bug with the library, nor an issue we can deal with at this point in time.