Partial source context in Release with multi-project MAUI apps

[NathanielJS1541]

Package

Sentry.Maui

.NET Flavor

MAUI

.NET Version

9.0.301

OS

Android

OS Version

Android API 34/35.

Development Environment

Visual Studio v17.x

SDK Version

6.10.0

Self-Hosted Sentry Version

No response

Workload Versions

Installed Workload Id      Manifest Version       Installation Source
---------------------------------------------------------------------
android                    35.0.61/9.0.100        VS 17.14.36203.30
ios                        18.4.9288/9.0.100      VS 17.14.36203.30
maccatalyst                18.4.9288/9.0.100      VS 17.14.36203.30
maui-windows               9.0.51/9.0.100         VS 17.14.36203.30
wasm-tools                 9.0.6/9.0.100          VS 17.14.36203.30

Use `dotnet workload search` to find additional workloads to install.

UseSentry or SentrySdk.Init call

            var builder = MauiApp.CreateBuilder();
            builder
                .UseMauiApp<App>()
                .UseSentry(options => {
                    options.Dsn = "";

                    // Set SDK to debug mode, as this is a repro app.
                    options.Debug = true;

                    // Application release and distribution.
                    options.Release = $"maui-sentry-test@{AppInfo.VersionString}";
                    options.Distribution = AppInfo.BuildString;

                    // Set the environment based on build configuration.
#if DEBUG
                    options.Environment = "Development";
#else
                    options.Environment = "Production";
#endif
                })

Steps to Reproduce

1. Clone my repro project.
2. Follow the README.md to configure the Sentry application and organisation slugs, and DSN.
3. Build the app in Debug mode, and deploy to a device (i.e. Android).
4. Launch the app and click the CommonService Exception button.
5. Check your Sentry issues for the report, observe the behaviour from the "Expected" section.
6. Build the app in Release mode, and deploy to a device.
7. Launch the app and click the CommonService Exception button.
8. Check your Sentry issues for the report, observe the behaviour from the "Actual Result" section.

This issue seems to be exhibited specigically when an exception occurs in a project separate to the main MAUI app, and the build is trimmed / optimised.

Expected Result

The stack trace will show line numbers and source context for all managed source:

Actual Result

In release mode, the stack trace only shows line numbers and source context for code within the "App" project:

I will note that I'm also seeing similar issues on iOS, but currently I can only deploy the test app to the simulator and it doesn't seem to be an issue there. Windows doesn't seem to show the same issue.

[NathanielJS1541]

Another thing that might be worth noting is that I'm seeing similar issues with areas that appear to be optimised, such as methods that are inlined. For example, clicking the InternalService Exception on a Release Android build results in the following stack trace:

This leads me to believe that these issues may be to do with trimming / optimisations, and may need to be documented somewhere.

If I prevent the method being inlined, I get the stack trace I would expect:

Although these cases appear to be different as the stack trace doesn't show the method call in the stack trace at all.

[NathanielJS1541]

An example of this that we're seeing in production (that lead me to believe this issue was related to our multi-project structure) is this:

In green, you can see code in our "App" project with line numbers and source context, and in red two method calls to our "Core" project with no line numbers or source context.

[NathanielJS1541]

I've been sent #4176 and #2180 by Sentry support, which may be related.

[jamescrosswell]

Thanks @NathanielJS1541 and thanks for the repro.

It might take me a little while to get to the bottom of this one (anything that only happens in release mode can be a bit tricky to debug).

Let's focus on the Android side of things first and then see if any of what we uncover there can be applied to iOS. They're quite different beasts (only very small portions of Android applications get AOT compiled and Mono is only ever used on iOS when running on a simulator with the interpreter enabled).

[NathanielJS1541]

@jamescrosswell yeah I figured as much. Let me know if there's anything I can help with. I'll keep having a look to see if I can see anything else too.

One thing I did notice is that in the Sentry web interface, it doesn't seem to try and load the "images" for the "Common" project in Release:

Whereas in Debug, it loads both "images" the different projects:

You can see it's also showing missing symbolication for various libraries too in Debug, which it isn't in Release.