Errors are not being reported to Sentry

[ianb]

We have a buildSettings pointing to our prod Sentry, but I don't see any errors there. This is implausibly quiet.

[jaredhirsch]

can you manually trigger an error, say, by turning off your network connection, then look for a sentry ping attempt in the devtools network tab?

[jaredhirsch]

I'll take a look at this

[ianb]

FYI, I double-checked the buildSettings.js setting, and it is correct

[jaredhirsch]

I exported current master into current mozilla-central, built firefox, and Sentry pings are being sent to the correct URL (https://sentry.prod.mozaws.net/api/139/store/? followed by an enormous query string).

The easiest way to test is to switch off wifi, take a screenshot, and try to save it to the server.

This doesn't explain why we aren't seeing anything in the Sentry dashboard, but I did observe that old profiles have an IndexedDB error on today's Nightly, which causes Screenshots to never load, instead crashing on startup.

I'll try next using the ./bin/run-addon approach.

[jaredhirsch]

I can also confirm that Sentry endpoints are pinged if the SCREENSHOTS_SENTRY env var is set when you invoke ./bin/run-addon. Using this incantation:

SCREENSHOTS_SENTRY="https://97d8afa496f94764ae255e739b147f4b@sentry.prod.mozaws.net/139" ./bin/run-addon --bootstrap

I was able to turn off wifi, try to save a shot, then observe a POST attempt to the Sentry endpoint.

edit: fix typo

[jaredhirsch]

I'm waiting to get Sentry access. I"ll continue debugging once I can view the dashboard.

[jaredhirsch]

Seems like the issue may be that the addon pings are coming from a randomish moz-extension URL, and may be getting dropped by sentry.

Removing the scary firefox-55 blocker label 🎉

[ianb]

Sadly it looks like request from the background page have no referrer or origin, so there's nothing to whitelist in Sentry. I'm looking into whether we should just ship with the Sentry Private DSN.

More discussion in Bug 1369162