Sentry 6.8 crash on iOS devices in AOT mode (ie: release testflight)

[softlion]

Package

Sentry.Maui

.NET Flavor

Mono

.NET Version

10.0.302

OS

iOS

OS Version

26

Development Environment

Other

Other Error Monitoring Solution

No

Other Error Monitoring Solution Name

No response

SDK Version

6.8.0

Self-Hosted Sentry Version

No response

Workload Versions

N/A

UseSentry or SentrySdk.Init call

N/A

Steps to Reproduce

N/A immediate crash, reported in ... sentry

Expected Result

no crash

Actual Result

Sentry report:

Attempting to JIT compile method 'void Sentry.Extensions.Logging.SentryStructuredLogger:Log<Microsoft.Extensions.Logging.FormattedLogValues> (Microsoft.Extensions.Logging.LogLevel,Microsoft.Extensions.Logging.EventId,Microsoft.Extensions.Logging.FormattedLogValues,System.Exception,System.Func`3<Microsoft.Extensions.Logging.FormattedLogValues, System.Exception, string>)' while running in aot-only mode. See https://learn.microsoft.com/xamarin/ios/internals/limitations for more information.

No issue on 6.0.0 (last known version that work, other versions are untested, will test them)

[linear-code]

NET-779

[jamescrosswell]

@softlion are you able to provide a way that I can reproduce this? It's hard to guess what the problem might be based off the information provided.

There don't appear to be any meaningful changes to the StructuredLogger from version 6.0.0:

Can you reproduce this in a fresh MAUI application with Sentry added to it, when trying to compile AOT?

[github-actions]

👋 Thanks for the report! We've added the Needs Reproduction label because we need a minimal reproduction to investigate further.

Please provide a link to a public GitHub repository that reproduces the issue with as little code as possible. Our repro guide has tips on how to create one.

Some quick hints:

• Start from a fresh dotnet new console (or similar) project
• Add only the Sentry NuGet package(s) relevant to the bug
• Include the exact SDK version number and your SentrySdk.Init / UseSentry call (with the DSN blanked out)

Alternatively, if the issue only manifests in your own codebase, you could try gradually removing code until you have a minimal repro.