feat(apple): Explain unsymbolicated stacktraces

Add an entry to the troubleshooting guide on a bug leading to
unsymbolicated stacktraces for non fatal events.

Author: philipphofmann

docs/platforms/apple/common/troubleshooting/index.mdx

@@ -203,3 +203,9 @@ you might see a compilation error `'required' initializer 'init(from:)' must be
 * `SentryUser`
 
 You can fix this by not subclassing the affected classes. Strictly speaking, this is a breaking change, but these classes are not intended to be subclassed. If you have a strong reason to subclass them, please open a [GitHub issue](https://github.com/getsentry/sentry-cocoa/issues/new/choose).
+
+## Unsymbolicated stacktraces for non fatal events such as captureError or captureMessage
+
+Cocoa SDK versions [8.51.1](https://github.com/getsentry/sentry-cocoa/releases/tag/8.51.1) and [8.52.0](https://github.com/getsentry/sentry-cocoa/releases/tag/8.52.0) have a bug that causes unsymbolicated stacktraces for non-fatal events, such as`captureError`, `captureMessage` or `captureException`. All or most stacktrace frames are then marked as `redacted` by Sentry. This bug doesn't impact fatal events or crashes.
+
+Please update the Cocoa SDK to version [8.52.1](https://github.com/getsentry/sentry-cocoa/releases/tag/8.52.1) or above or stay on version [8.51.0](https://github.com/getsentry/sentry-cocoa/releases/tag/8.51.0) or below to fix this problem.