-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
Support Source Context #132
Comments
Currently blocked by dart-lang/sdk#44325 |
The linked issue mentions that most of it is now possible via |
Hello guys, any news about this issue? This is really important for us 😬 |
@augustorsouza we'd like to do it but we didn't spend much time investigating it yet, we don't even know if it's supported ootb by the flutter/dart tooling. just to be clear, this is about showing the source code around the stack trace on sentry, not really related to source maps or anything, it's a nice feature indeed, but would you mind elaborating why is it important? interested in the use case, so we can prioritize. |
For Web, it works at some degree, see #417 (comment) |
We'll test if the new flag |
Relates to: getsentry/sentry-java#633 |
@vaind do you know if this is possible after your PRs on Dart/Flutter language/engine? |
not out of the top of my head, I'll check |
https://github.com/getsentry/sentry-dart-plugin already supports iOS does not work at all getsentry/team-mobile#42 (comment) |
I've managed (with a custom flutter build) to get an issue with absolute paths to sentry.io from Android. Weirdly though, each stacktrace source path contains "dispose" somewhere in the path - see https://sentry.io/organizations/sentry-sdks/issues/3734649639/events/1f7d76d638bf44dd8c069bc0a15c260f/?project=5428562 No idea where that comes from because the stack trace coming from edit: the same "dispose" is in the path on iOS: https://sentry.io/organizations/sentry-sdks/issues/3734649639/events/78f08f5fcd75451db6a64161b4b0133c/?project=5428562 - likely something we're adding along the way |
As for web, I'm confused... this issue linked above says it should work, but for some reason, It doesn't for me: https://sentry.io/organizations/sentry-sdks/issues/3734775388/events/e14d18b2b90c4c97815245624ed4757e/?project=5428562 |
Does the SDK set that in the |
I've checked that last week and didn't find any occurrence of the "dispose" as a string anywhere in the dart, java or native SDK. |
please do - I've posted on discord in the |
There's no uploaded sourcemaps for this release. |
hmm, that looks like an error. SENTRY_RELEASE env var is set in |
web - it loaded the cached version from a previous run. when I made sure I use the version I've just built, in-app source codes work fine - https://sentry.io/organizations/sentry-sdks/issues/3741285487/events/0c0429bd595840b6a5117b755a3f0da8/?project=5428562 |
@vaind I believe this is completed on our side and it works OOTB when the source context is uploaded, right? |
@marandaneto not at all, there's an open PR on Flutter to enable this option (flutter/flutter#114767) and there's an UI issue that the sources don't show up on sentry.io (looking into that - https://discord.com/channels/621778831602221064/809895882987536395/1068962301228617830) |
UI work is being tracked here. |
UI is fixed and the flutter PR has landed as well. In other words, this is "done" and should start working automatically with the next Flutter release. I'll keep my eye on this and check in a couple of days against Flutter master to see if everything seems in order. Keeping the issue open for now |
@vaind did you manage to check whether this is working now? |
Works with the latest beta tag (but not in with the
https://sentry-sdks.sentry.io/issues/3979346432/events/a64d54c3c3a44eeba76ddf22f2bf9800/?project=5428562 |
Originally posted on flutter: flutter/flutter#63276
Users would like to see the source context around the stack trace. This is a feature supported in Python, JavaScript and other script languages. Native has this support with source bundles.
Relates to (Java, .NET)
The text was updated successfully, but these errors were encountered: