From 4588f270fd0c49ff7df83c07607bfb804b15201e Mon Sep 17 00:00:00 2001 From: bitsandfoxes Date: Wed, 27 Aug 2025 11:34:45 +0200 Subject: [PATCH] Added Mono & Line Numbers to Known Limitations --- docs/platforms/unity/troubleshooting/known-limitations.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/platforms/unity/troubleshooting/known-limitations.mdx b/docs/platforms/unity/troubleshooting/known-limitations.mdx index 98ff73b47835af..eb9f9be570d2bb 100644 --- a/docs/platforms/unity/troubleshooting/known-limitations.mdx +++ b/docs/platforms/unity/troubleshooting/known-limitations.mdx @@ -30,6 +30,10 @@ The exception provided by Unity that is getting captured by the logging integrat Currently, it is not possible for the SDK to distinguish between the user calling `Debug.LogException` and the SDK capturing an unhandled exception. To capture an exception and mark it as handled you can call `SentrySDK.CaptureException` instead. +### Line Numbers Missing when Building with Mono + +When building with Mono, make sure to set the `ManagedStrippingLevel` to `None`. Otherwise, Unity will strip the debug information from the assembly, which will cause the SDK to fail to retrieve the debug ID that allows connecting the assembly to the correct debug symbols for symbolication. + ### C++ as Part of the Stack Trace Your stack traces might contain C++ frames. This might be because: