Source Maps fail to process because Raygun "can't find uploaded files"

I am trying to work with the Crash Reporting Source Map Center to get an unminified stack trace appear for errors in my web application, but rayugn is giving me the error "The minified files

I have written Powershell scripts that upload my files to the raygun source map api endpoint upon deploy of my application, but Raygun is failing to process my source maps and show me the unminified stack trace.

Here are my steps:

1. Upload minified .js bundle to Raygun via Api endpoint [Result is in screenshot 1 below]
2. Run my application locally
3. Trigger an error in the application
4. The error shows up in Raygun Crash reporting with an unminified stack trace and the button "Reprocess this error for source maps" is visible
5. I click the button to re-process for source maps
6. After a sometimes lengthy (about 1 or more minutes) wait period I get an error message saying that the minified files for the stack trace cannot be obtained [error message and stack trace in screenshot 2 below

I followed this same process roughly two weeks ago and got the desired result, an unminified stack trace of the correct sections of my code [Screenshot 3 below]

Edit: Google Chrome is able to process the sourcemaps successfully and allow me to debug my unminified code from the minified bundles.

Source map center showing uploaded minified JS, and js.map files Error Processing Source maps and un-minified stack trace Successful source map processing about 2 weeks ago Note: Not executing on localhost, but still on a private server. I was able to get the same result on localhost

Thank you!

Hi Samuel,

Thanks for reporting this. Some error were being incorrectly attached during manual mapping. This issue has just been resolved and the error you referenced now maps correctly.

Best regards,
Alex

Hi Alex,

Thank you very much for replying to my issue. My stack trace with full source maps now displays fully unminified as desired.

That takes care of the error given in screenshot #2 in the post. However, I am now gettting a similar error when I try to click the "reprocess for sourcemaps" button for a stacktrace which I only have partial sourcemaps for. The error is shown in the first screenshot in this post, lets call it #2-1.

As you can see from screenshot #3 above (reposted as screenshot #2-2 below), I was previously able to process a stack trace for which I only had partial sourcemaps. Unfortunately, for a certain library (not angular as in the screenshot), I will only be able to access the minified JS, and won't be able to provide source maps for that library file.

Is this functionality going to be restored?

Thank you, Sam

Screenshot #2-1 Failed partial stacktrace Screenshot #2-2 Successful partial stacktrace from a couple weeks ago Screenshot #2-3 SourceMap center for screenshot #2-1

Hi Sam,

I believe the reason the files weren't discovered was due to some leading or trialing whitespace in the URL field. After stripping the whitespace mapping worked as expected. I've also ensured that whitespace is automatically stripped for future uploads to the source map center to prevent this from happening again.

Best regards,
Alex

Hi Alex,

Thank you for your quick reply and fixes. Everything appears to be working as expected, thank you so much. I'm excited to roll this out to production.

Best, Sam

Happy to help : )

Cheers,
Alex

Hmm It appears I'm getting a different error now. I've started a new thread: https://raygun.com/forums/thread/47508#47507 as it appears to be slightly different than this issue.

Thanks again,

Sam