Bug: Breadcrumb throws an exception when window.fetch is passed a Request object instead of a URL string

[periodic]

Version: 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. :)

[periodic]

[periodic]

I added a dummy handler that throws an exception to test my Raven JS library upgrade, got the following:

[LewisJEllis]

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.

[jedrichards]

Also got something similar going on,

We are loading Raven 3.14.0 via your CDN. Testing on Chrome 57 macOs. Also calling fetch like fetch(requestObj) ...

[quicksnap]

Also encountering this. First time using Sentry, too.. doh!

[quicksnap]

I downgraded to Raven 3.10.0 and now I can report errors correctly.

[jedrichards]

I just changed my fetch call signature from,

fetch(new Request(ops))

to,

fetch(url, ops)

and it fixed it.

[timtyrrell]

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.