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.
Bug: Breadcrumb throws an exception when window.fetch is passed a Request object instead of a URL string
See original GitHub issueVersion: 3.14.0 Browser: Chrome 56 OS: Linux Plugins: none
When reporting exceptions in my application after upgrading from 3.10.0 I’m getting an error during reporting str.substr is not a function.
Digging into the code it looks like the problem is that Raven is logging fetches for the breadcrumbs, but it expects the first argument of the fetch to be a URL. However, it is valid for it to be a Request object. This is causing the type error because the Request object is stored in the "url" field and is expected to be a string on line 1429.
Expected behavior is that the library handle fetch breadcrumbs and report errors. 😃
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for the report, @periodic. I haven’t looked at our fetch instrumentation, but I’m familiar with fetch taking either a url string or a Request object, so this sounds plausible. I’ll investigate.
We haven’t been getting errors for a long time because of this… I can confirm that 3.13.1 is the last version that works with Request.