From 3b02756f52ad29ea15b7eb747dd0e07fb80a18d1 Mon Sep 17 00:00:00 2001 From: James Crosswell Date: Mon, 18 Aug 2025 14:42:32 +1200 Subject: [PATCH 1/2] Troubleshooting symbolication on Apple platforms - .NET --- .../dotnet/common/troubleshooting.mdx | 38 +++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/docs/platforms/dotnet/common/troubleshooting.mdx b/docs/platforms/dotnet/common/troubleshooting.mdx index 550344ef42e49..bc7a001afd3a5 100644 --- a/docs/platforms/dotnet/common/troubleshooting.mdx +++ b/docs/platforms/dotnet/common/troubleshooting.mdx @@ -4,6 +4,44 @@ sidebar_order: 9000 description: "Learn more about how to troubleshoot common issues with the .NET SDK. " --- + + +## Stack traces are not symbolicated on iOS, macOS and Mac Catalyst + +When building .NET MAUI applications in release mode for iOS, macOS, or Mac Catalyst, you may see unsymbolicated stack traces in Sentry, where function names appear as memory addresses instead of readable method names. + +This issue is caused by a mismatch between the uploaded debug files and the debug information in the running application. + +This is **a problem in the .NET SDK** that affects how debug information is handled when building for Apple platforms in release mode. This issue has been reported to Microsoft and is being tracked in the .NET runtime repository. + +If this issue affects your application, please: +1. Visit the [.NET runtime issue](https://github.com/dotnet/runtime/issues/118700) +2. Add a reaction (👍) to indicate this affects you +3. Consider adding a comment describing your use case + +This will help Microsoft prioritize the fix based on community impact. + +### Workarounds + +Until the issue is resolved properly, symbolication on Apple platforms is only possible by disabling stripping. For example, by adding the following to your `*.csproj` file(s): + +```xml + + false + +``` + +**Important Note**: This may significantly increase the size of your application. + +### Affected versions + +This issue affects: +- .NET 9 applications targeting iOS, macOS, and Mac Catalyst +- Applications built in release mode with trimming enabled +- Specifically impacts the `net9.0-ios*` target frameworks + + + ## Sentry CLI not configured The following message may appear in your build output: From 455bd5ae009e33a63851993fc427e536cf0ab63a Mon Sep 17 00:00:00 2001 From: James Crosswell Date: Mon, 18 Aug 2025 14:53:55 +1200 Subject: [PATCH 2/2] Update troubleshooting.mdx --- docs/platforms/dotnet/common/troubleshooting.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/platforms/dotnet/common/troubleshooting.mdx b/docs/platforms/dotnet/common/troubleshooting.mdx index bc7a001afd3a5..6323654a9b021 100644 --- a/docs/platforms/dotnet/common/troubleshooting.mdx +++ b/docs/platforms/dotnet/common/troubleshooting.mdx @@ -10,9 +10,7 @@ description: "Learn more about how to troubleshoot common issues with the .NET S When building .NET MAUI applications in release mode for iOS, macOS, or Mac Catalyst, you may see unsymbolicated stack traces in Sentry, where function names appear as memory addresses instead of readable method names. -This issue is caused by a mismatch between the uploaded debug files and the debug information in the running application. - -This is **a problem in the .NET SDK** that affects how debug information is handled when building for Apple platforms in release mode. This issue has been reported to Microsoft and is being tracked in the .NET runtime repository. +This is due to **a problem in the .NET SDK** that affects how debug information is handled when building for Apple platforms in release mode. This issue has been reported to Microsoft and is being tracked in the .NET runtime repository. If this issue affects your application, please: 1. Visit the [.NET runtime issue](https://github.com/dotnet/runtime/issues/118700)