Crash logs not getting on Sentry Dashboard

[scarlet olive]

I am using Self Hosted Sentry , and i already integrated Sentry on. my Kmp App , and initialized it correctly , All the logs which i manually write like Sentry.CaptureMessage("") these logs gets correctly on Dashbaord , however the crash logs arent appearing. How can i fix it , i need crash logs as well

[lucid roost]

Hi @scarlet olive. I'm happy to dig into this for you! I'll check my internal sources for answers to your question! :wave:

---

If your manually captured logs (e.g., Sentry.captureMessage("")) are appearing in your Self-Hosted Sentry dashboard, but crash logs are not, this is a common issue reported by other users integrating Sentry with KMP (Kotlin Multiplatform) and iOS/Android apps.

Here are some key points and troubleshooting steps based on the knowledge sources:

1. Crash Logs May Not Be Sent Before App Terminates
   In both Android and Apple platforms, crash logs can be lost if the SDK does not have enough time to send them before the app is terminated. Sentry is working on improvements to ensure logs are sent on the next app restart, but currently, you may need to relaunch the app after a crash to allow the SDK to send any pending crash reports. Make sure to test this by crashing the app, then reopening it and checking if the crash appears in the dashboard after the restart
   Missing Logs for Crashes (Apple)
   Missing Logs for Crashes (Android).

2. KMP/iOS Native Crashes Not Reported
   There are known issues where iOS native crashes are not reported when using Sentry KMP, even if manual events are sent successfully. This has been reported in the community, and there is no confirmed workaround in the knowledge sources. If you are using Sentry KMP, you may be affected by this limitation
   Kotlin SDK Issue: iOS Native crashes are not being reported to Sentry.

3. Check DSN and Self-Hosted Configuration
   For self-hosted Sentry, ensure your DSN is correctly configured and points to your actual Sentry instance domain, not just nginx or a placeholder. An incorrect DSN can cause events (especially crash events) to not reach your server. You can check and update the DSN in the Sentry UI under Admin → Settings → General → Root URL
   Self-Hosted Sentry DSN Troubleshooting.

4. SDK Debug Logs
   Enable debug logging in your Sentry SDK configuration. This will print detailed logs to your console or log files, which can help you identify if crash events are being captured and attempted to be sent, or if there are errors in the process
   Where can I view my Sentry debug logs?.

5. Check for HTTP Errors (e.g., 301 Redirects)
   If you see errors like HTTP 301 (Permanent Move) in your Sentry SDK logs, your self-hosted Sentry may be misconfigured, causing the SDK to fail to upload crash envelopes. Make sure your Sentry instance is accessible at the DSN URL and that there are no misconfigured redirects
   React Native SDK Issue: Error events are not recorded in Sentry dashboard.

Summary of Actions:

• After a crash, always relaunch the app to allow Sentry to send pending crash logs.
• Double-check your DSN and self-hosted Sentry URL configuration.
• Enable and review SDK debug logs for errors or warnings.
• If using KMP, be aware of current limitations with iOS native crash reporting.
• Look for HTTP errors in your logs that may indicate server misconfiguration.

If after these steps crash logs still do not appear, you may be encountering a known limitation or bug, especially with KMP/iOS, and it may require waiting for an SDK update or further investigation from the Sentry team.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: