New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Events missing debug ID #11865
Comments
Hi,
I think this is the core question. Given wp-sentry isn't officially maintained by us I'm gonna tag @stayallive - do you have an idea why the browser SDK might not be attaching debug ids in wp-sentry? The relevant code is here. I just skimmed over wp-sentry and it seems it uses the browser SDK >7.47.0, so it should work 🤔 |
Also, to folks following this issue: Can you confirm that no errors sent from the browser SDK have debug ids? (Sorry if I missed this in the various tickets and threads around this issue) |
Could this be a path mapping issue? I'm assuming OP develops a plugin or theme and they might not be in the path where Sentry would expect it to match uploaded sourcemaps. There is no client config for this right? We have no special config set to disable anything as far as I'm aware, we bundle the CDN version of the builds and the latest plugin version bundles Anything I'm missing that would not client configuration to make this work? |
TLDR: The problem seems to be gone on new issues concerning the same JS file. But, even though Sentry shows the correct line and content of the source file, the path it's showing is wrong and if I click on it, it gives me a 404. Hi, I'm the person this issue was opened for 👋🏻 @stayallive you're right, I'm working on our website's theme, and the content of the folder Before this issue was opened there's been a long discussion between me and Stella via tickets, so you're all probably lacking a lot of context here. Basically I had this issue in Sentry where Other issues concerning files in the same folder as the above were mapping correctly, eg: https://newzoo-com.sentry.io/share/issue/00f6add9b4064aa685640939fa69ae87/ Although I'm only noticing now something odd. The two issues above show different paths to the source: The issue that doesn't map, shows The issue that maps correctly, shows ↑ this one, even though is the one that works, shows a wrong path to the source:
To sum it up, So ironically the one that did not work was the one with the correct mapping. I suspect that's why that was happening, though I have no idea why since both files were generated by the same webpack config. Is this something on Like I said above, I can see the correct content in the stack trace, but the path is not correct for some reason, so if I click on it I get a 404: I went ahead and deleted all Code Mappings, recreated it by clicking on CleanShotX.-.Arc.16.05.2024.at.16-00-40.mp4 |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
7.108.0
Framework Version
No response
Link to Sentry event
No response
SDK Setup
Provided in the shadow ticket. Note that they are using wp-sentry.
Steps to Reproduce
webpack --watch --mode development
(which, as opposed to what the documentation says, it still uploads the source maps to Sentry, although it shouldn't)webpack --mode production
to generate the dist files.Expected Result
Events are source mapped correctly.
Actual Result
After looking through how the rest of their events appear in Sentry, it looks like they are most likely generating and uploading source maps correctly. According to their logs, their source maps have debug IDs, and I am able to find them in their project settings too. However, their events do not have debug IDs, which is where things go wrong.
Since we do not have debug IDs available, we would fall back to the legacy source mapping method which uses releases, however, their source maps are not connected to their releases, so it's not possible to show readable code. Even if they were, though, the fact that their abs_path values in an event are not an exact match to the names of their uploaded files (there is a
ver
parameter appended at the end of the file name that does no exist in the uploaded source maps) would prevent Sentry from deminifying their stack traces still.For a specific file, it is also unusual to see row 1 column 0, as it would most likely map to nothing even in working source maps.
So there are 2 issues to address here:
Why are there no debug IDs in your events
Why is that specific bundle showing row 1 column 0
┆Issue is synchronized with this Jira Improvement by Unito
The text was updated successfully, but these errors were encountered: