Repository navigation
Unable to get exception line numbers to show #3983
Description
Package
Sentry.Maui
.NET Flavor
.NET
.NET Version
9.0
OS
Android
SDK Version
14.0
Self-Hosted Sentry Version
No response
Steps to Reproduce
I initialize sentry in my MauiProgram.cs like this:
.UseSentry(options => {
options.Dsn = "";
options.Debug = true;
options.AttachStacktrace = true;
})
Then I try to capture exceptions like this:
try
{
...
}
catch (Exception ex)
{
SentrySdk.CaptureException(ex);
SentrySdk.CaptureMessage(ex.ToString(), SentryLevel.Info);
}
I thought with CaptureException would have been enough. But since no line numers are showing, I also tried with CaptureMessage. No luck:
Then I thought I could get line numbers information by uploading Debug Information Files. Which I did, but exceptions are still not showing exception line number information.
Is sentry able to give me this information?
Am I missing anything?
I'm unable to find the problem without the line number information.
Expected Result
I would expect to find the line number where the exception is produced. I'm unable to find the problem without that information.
Actual Result
Posted above
Metadata
Metadata
Assignees
Labels
No labels
Projects
- Status
- Status
Activity
jamescrosswell commentedon Feb 19, 2025
Older (perhaps related) similar issue:
jamescrosswell commentedon Feb 20, 2025
Hey @nk-alex,
It looks like you've uploaded some symbols and sources to Sentry so if you're still not seeing source context for exceptions, it seems likely Sentry isn't able to resolve to correct symbols/source.
One thing to ensure is that the version of the code that is running when exceptions are captured and sent to Sentry is exactly the same version that was built when you uploaded the symbols/source to Sentry. Otherwise you might end up with a different debug_id in the PE file for the application versus the debug_id that is included in the symbols/source being uploaded. See here for more details.
If you're doing this on a local development machine then basically you'd:
nk-alex commentedon Feb 20, 2025
Hi @jamescrosswell, the process I've been following is pretty much what you have described:
I can get more information from the error by checking Breadcrumbs, but not much more than this. I don't know where (line) it's happening:
jamescrosswell commentedon Feb 20, 2025
@nk-alex it would be great to get a copy of the JSON file for that event, to compare the debug_id in the event with the debug_id on the PDB that you uploaded to Sentry. If these match then that's the first pre-requisite to getting this all working.
nk-alex commentedon Feb 21, 2025
@jamescrosswell My json for the event doesn't contain information for debug_id:
43 remaining items
jamescrosswell commentedon Mar 6, 2025
Just an update, I've identified the issue here. All that's left to do now is implement the solution.
For details, see the parent issue:
nk-alex commentedon Mar 7, 2025
Thank you all for the support and dedication. I'll keep an eye on this issue, tell me if I can provide any helpful logs