Skip to content

Conversation

@lforst
Copy link
Contributor

@lforst lforst commented May 30, 2023

I gave the current source map troubleshooting page a pass and updated it for the new debug ID process.

Disclaimer: We'll probably run into issues with debug IDs in the future which we don't know of yet. The current troubleshooting page is probably not very in-depth but I am planning to extend it whenever users run into issues.

@vercel
Copy link

vercel bot commented May 30, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sentry-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 31, 2023 7:48am

@lforst lforst force-pushed the lforst-rework-sourcemap-troubleshooting-section branch from 2df06d7 to e1c0e0b Compare May 30, 2023 10:44
@lforst
Copy link
Contributor Author

lforst commented May 30, 2023

@Lms24 @mydea It would be very nice if any of you could check whether the sections on debug IDs make sense to you.

@lforst lforst marked this pull request as ready for review May 30, 2023 10:56
Copy link
Contributor

@shanamatthews shanamatthews left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Little tweaks to follow our style guide and make this more readable

<Note>

Alternately you can specify which files to upload. For example:
Chances are, you set up source maps for Sentry a while ago. Since then we updated a lot of our tooling to make the process around source maps easier.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Chances are, you set up source maps for Sentry a while ago. Since then we updated a lot of our tooling to make the process around source maps easier.
Sentry recently updated our tooling to make the process of uploading source maps easier.


Alternately you can specify which files to upload. For example:
Chances are, you set up source maps for Sentry a while ago. Since then we updated a lot of our tooling to make the process around source maps easier.
We recommend you upgrade your tooling to the newest versions, as that is usually easier than to troubleshoot the legacy method.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We recommend you upgrade your tooling to the newest versions, as that is usually easier than to troubleshoot the legacy method.
If you're using an older version of the Sentry SDK (version 7.47.0 or older), we recommend upgrading your tooling and switching to the new source maps process, as it is easier to troubleshoot than the legacy method.

Luca Forstner and others added 2 commits May 31, 2023 08:34
Co-authored-by: Shana Matthews <shana.l.matthews@gmail.com>
@lforst
Copy link
Contributor Author

lforst commented May 31, 2023

@shanamatthews those were amazing suggestions. Thank you! 🙏

Just to vibe check my changes a bit: As a person not working on the source map process, do the instructions somewhat make sense to you? Ideally, I would like to get rid of, or even better, improve, all the sections that make somebody go "what the f do they want from me here".

@lforst lforst merged commit 16eed33 into master May 31, 2023
@lforst lforst deleted the lforst-rework-sourcemap-troubleshooting-section branch May 31, 2023 11:12
@github-actions github-actions bot locked and limited conversation to collaborators Jun 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants