# Which mobile crash reporting services give the most detailed diagnostics?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">I’m comparing mobile crash reporting services based on diagnostic depth. Which tools go beyond a stack trace and show enough context to make difficult crashes reproducible?</p><ul>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/sentry/reviews"><strong>Sentry</strong></a><strong>:</strong> Combines breadcrumbs, session replay, user context, API activity, and repository-linked stack traces.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/embrace-io-embrace/reviews"><strong>Embrace</strong></a><strong>:</strong> Maps full mobile sessions to crashes, exceptions, application-not-responding errors, out-of-memory events, and network failures.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/google-firebase-crashlytics/reviews"><strong>Firebase Crashlytics</strong></a><strong>:</strong> Adds device model, operating system, battery state, rooted status, app version, and event timelines.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/raygun/reviews"><strong>Raygun</strong></a><strong>:</strong> Provides granular diagnostics down to the affected line of code.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/rollbar/reviews"><strong>Rollbar</strong></a><strong>:</strong> Offers telemetry and RQL for investigating patterns such as sudden timeout increases.</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Sentry and Embrace appear strongest for reconstructing hard-to-reproduce sessions.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Which category of crash remains difficult even when detailed diagnostic data is available?</p>

##### Post Metadata
- Posted at: about 2 months ago
- Author title: Marketer
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;&lt;span style=&quot;color: rgb(0, 0, 0);&quot;&gt;The other category that resists diagnostics is the one where no report is generated at all. Watchdog terminations and some background kills stop the process without giving the SDK a chance to run its handler, so what you get is an absence rather than a stack trace, and the only way to see it is inferring from sessions that end without a clean exit. That makes session reconstruction rather than crash capture the relevant capability, which is why Embrace mapping full sessions to events gets credited here. Worth checking whether a tool reports a session-end reason at all, since that is the signal that surfaces silent terminations.&lt;/span&gt;&lt;/p&gt;

##### Comment Metadata
- Posted at: 3 days ago
- Author title: Tech Consultant



### Comment 2

Memory and OOM crashes are the category where even detailed diagnostics often fall short. Embrace mapping out-of-memory events to full sessions is specifically useful there, because the crash itself rarely tells you which sequence of screens and network calls exhausted the memory budget.

##### Comment Metadata
- Posted at: about 2 months ago
- Author title: Writer





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4