Trying to figure out Release Management with Sentry: Day Two.
I got sentry/node to work, sentry/browser refuses to send any exceptions. I managed to upload files for my release, but when I trigger an error for our node app, the release is not shown anywhere and the file in which the error happened isn't even shown anywhere...
Slow progress: Figured out how to report issues so that they are tied to a release and environment. Artifacts are uploaded, but still don't seem to be used in the traceback...
Slow progress: Realized that in my error test view, the console says this: "ReferenceError: myUndefinedFunction is not defined" vs. "Uncaught ReferenceError: thisMethodDoesNotExist is not defined" -- I guess the "Uncaught" here is important.
I think this is because I tried to call a non-existant function in the render() of a view that gets loaded by loadable... maybe the browser sees that this chunk has a syntax error and crashes and this is assumed to be a caught error? just wild guesses.
@getsentry any idea why this view does not result in a Sentry issue when I click a react-router-dom <Link> that leads to this view?
Current status: Moving on to the Node app. React reports good enough and sourcemaps seem to work. Still unclear why some obvious errors on React are not reported, will have to revisit that later. Node SSR app seems to be a harder nut to crack, as it never uses the sourcemaps...
Events are coming in, but sourcecode and sourcemaps (basicaly, server.js and http://server.js.map ) are never found. It's gotta be something about this app:/// thing... I use `--rewrite` when uploading the two files as artifacts...
Why is it with such problems, that you google your brains out, find nothing, go to sleep (or have dinner), then google again and find a solution within five minutes.
You can follow @mbrochh.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: