Is it not recommended to track crashes with Mixpanel?

Hi j o., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋

Based on the knowledge sources provided, it is not recommended to rely on Mixpanel's automatic tracking of crash events. Here's why: Mixpanel's mobile SDKs have a legacy feature to automatically collect common mobile events, including app crashes. However, Mixpanel explicitly states that they don't recommend enabling this feature. The reason given is that these automatically tracked events rely on client-side state and can be unreliable.Specifically, the documentation states: "Mixpanel's mobile SDKs have a legacy feature to automatically collect common mobile events. We don't recommend enabling this, as these events rely on client-side state and can be unreliable."Mixpanel SDKs: iOS (Objective-C) provides more details on this, including how to disable automatic event tracking: "Ensure autotracked mobile events are disabled by setting trackAutomaticEvents to NO during initialization."While the automatic tracking does include a crash event ($ae_crashed), the recommendation is to not rely on this method for tracking crashes due to its potential unreliability.Instead, it's generally better to implement a more robust, server-side tracking solution for critical events like crashes, as this would provide more reliable and consistent data across platforms.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.