Sentry source maps are not working in many cases

Feedback
1

We serve our javascript app with source maps in production. Sentry is able to show the actual line of exception in many scenarios, but in many other it doesn’t use the source maps.

Here is one example where source maps are not used.

TypeError: Cannot read property 'id' of undefined
  at ? (/javascript/main.5d9894d0894808cd5872.bundle.js:1:1658714)
  at ? (/javascript/main.5d9894d0894808cd5872.bundle.js:1:402875)
  at N(/javascript/vendors.86242900678aea45894b.bundle.js:1002:7509)
  at ? (/javascript/vendors.86242900678aea45894b.bundle.js:1002:7044)
  at g(/javascript/vendors.86242900678aea45894b.bundle.js:208:4927)
  at ? (/javascript/vendors.86242900678aea45894b.bundle.js:1002:9154)
  at ? (/javascript/vendors.86242900678aea45894b.bundle.js:906:2511)
  at ? (/javascript/vendors.86242900678aea45894b.bundle.js:49:3463)
  at dispatch(/javascript/vendors.86242900678aea45894b.bundle.js:208:8090)
  at ? (/javascript/main.5d9894d0894808cd5872.bundle.js:1:1688336)
  at ? (/javascript/vendors.86242900678aea45894b.bundle.js:906:2502)
  at ? (/javascript/vendors.86242900678aea45894b.bundle.js:49:3495)
  at e.closeFlash(/javascript/vendors.86242900678aea45894b.bundle.js:208:6950)
  at close(/javascript/main.5d9894d0894808cd5872.bundle.js:1:694124)
  at ? (/javascript/vendors.86242900678aea45894b.bundle.js:385:120761)
  at f(/javascript/vendors.86242900678aea45894b.bundle.js:385:31422)
  at ? (/javascript/vendors.86242900678aea45894b.bundle.js:385:32778)
  at s(/templates/Processing-Coaching-Call-Recordings-qGfRogxcwp2HHhB115lHqg/view/tasks/kxJiqmAPLgXpY2hp4i5NRA:5:23557)
  at o(/javascript/vendors.86242900678aea45894b.bundle.js:838:6839)
2
  • Are there any errors displayed at the top of the issue details? Sourcemaps should show processing errors.
  • What browser is it reported from?
  • Does sourcemaps.io report any issues with your generated artifacts?
  • Are you uploading artifacts before recording errors?
3

Thanks David for the reply. Here is answer to your questions

  • Are there any errors displayed at the top of the issue details? Sourcemaps should show processing errors.
    Answer: I don’t see any specific message related to sourcemap processing errors. I do see errors like ‘There were 3 errors encountered while processing this event’ which I also see when the sourcemaps are used.
  • What browser is it reported from?
    Answer: Firefix(65+) and Chrome(72+)
  • Does sourcemaps.io report any issues with your generated artifacts?
    Answer: No errors but it does report many warnings
  • Are you uploading artifacts before recording errors?
    Answer: No we have it available publicly i.e. along the minified js on the same server and I do see
    //# sourceMappingURL=main.34ef0e94e1cd89e2680f.bundle.js.map included as second line in the minified file
4

Its possible you’re hitting scraping errors - we set a backoff timer on scraping failures so it means there could gaps. I’d try pushing the sourcemaps into the release artifacts and see if that resolves things.