Source Context for internal projects not showing

[lxalln]

Package

Sentry.AspNetCore

.NET Flavor

.NET

.NET Version

8.0.0

OS

Linux

SDK Version

4.9.0

Self-Hosted Sentry Version

No response

Steps to Reproduce

The project is configured like this:

<PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <!-- Configure Sentry org and project -->
    <SentryOrg>…</SentryOrg>
    <SentryProject>…</SentryProject>

    <!-- Sends symbols to Sentry, enabling symbolication of stack traces. -->
    <SentryUploadSymbols>true</SentryUploadSymbols>

    <!-- Sends sources to Sentry, enabling display of source context. -->
    <SentryUploadSources>true</SentryUploadSources>
</PropertyGroup>

This is the log that runs after dotnet publish…

Preparing upload to Sentry for project 'Services' (Release/net8.0): collecting debug symbols and referenced source code from bin/Release/net8.0/
  > Found 49 debug information files (48 with embedded sources)
  > Resolved source code for 0 debug information files
  > Prepared debug information files for upload
  > Uploaded 4 missing debug information files
  > File upload complete:

According to the debug-symbols page in Sentry, the sources have been uploaded:

Expected Result

I'm expecting to see our source code shown, like it does for the Microsoft dll.

Actual Result

I don't know if there's a way to link to an issue so you can see behind the scenes, if there is, let me know.

[bitsandfoxes]

Hey @lxalln, could you share the link to the issue with me? [email protected]
Thanks!

[lxalln]

I dropped you an email 👍🏻

On July 31, 2024, GitHub ***@***.***> wrote: Hey @lxalln <https://github.com/lxalln>, could you share the link to the issue with me? ***@***.*** ***@***.***> Thanks!

— Reply to this email directly, view it on GitHub <#3512 (comment)- 2260692935>, or unsubscribe <https://github.com/notifications/unsubscribe- auth/AAVHFVCIEA2CPOHXFDXKGV3ZPDZ6BAVCNFSM6AAAAABLYMVAFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGY4TEOJTGU>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[bitsandfoxes]

Thanks! There does seem to be something off. We're looking into it and will get back to you.

[bitsandfoxes]

It looks like something is misconfigured here. Sentry attempts to pull the source contexts but encounters a 403 while doing so.

This is related to getsentry/symbolicator#1507 which will help communicate that properly.

[bitsandfoxes]

Closing this with the changes introduced in getsentry/symbolicator#1507 should help with configuration. Please feel free to reopen this if the issue persists for you.

[lxalln]

@bitsandfoxes the recent updates have made no difference to this, I'm not seeing any errors when uploading sources, is this something I should be seeing?

The mis-configuration you mentioned is that on our side?

[bitsandfoxes]

It looks to me like like there's a conflict between Source Link and the uploaded sources. If you go into the actual json payload you can see each individual frame in the stacktrace having a source link attached to it. Sentry fails to retrieve the sources for your InApp frames (that's the 403 mentioned above).

What I don't get (yet) is why it's not falling back to the uploaded sources. Or why there is no error message detailing how to fix this.