December 9th, 2014
Introducing Parse Crash Reporting
Update: The Parse Crash Reporting tool is being deprecated in favor of great native solutions from Apple and Google. We will continue supporting Parse Crash Reporting until March 1, 2016. Find out how you can switch with these Apple docs and these Google docs. Questions or concerns can be shared to email@example.com.
We at the Parse London office are happy to announce Parse Crash Reporting: the simplest way to register, track, and resolve crashes in your apps. Being able to capture and fix crashes efficiently means fewer frustrated users and better retention--one of the most important metrics to any developer.
In the past, we've seen Parse developers use third-party crash reporting tools, but this approach required developers to manage several different SDKs, learn new APIs, and monitor many dashboards at once. We wanted it to be simpler. Part of Parse's core mission has always been to abstract away common tasks and streamline the developer's experience — so we built a way to manage crash reports right within Parse.
Say you've released a new version of your app that unfortunately "features" a newly introduced bug. Have no fear! All you have to do is enable Parse Crash Reporting, making the experience of handling crashes in your app much smoother than ever before. We've updated our iOS and Android SDKs to provide a simple and intuitive interface that detects the bug, pinpoints the issue, and generates a report allowing you to resolve problems quickly and easily. With this update, our SDKs automatically cache and resend your crash reports if connectivity is spotty. And, our backend tracks bugs on a per-version basis, so that if you've reintroduced an old bug in a new version of your app, Crash Reporting still ensures you'll notice and fix it as soon as possible—even if you've previously marked it as "resolved.”
Here's an example snippet showing how you can enable Parse Crash Reporting for Android:
Here's an example snippet showing how you can enable Parse Crash Reporting for iOS:
As you may have expected, the sending of crash reports from the client is asynchronous and takes place automatically in the background.
We're always looking to improve our products and would love to hear your feedback. Check out our guides, try it out, and let us know what you think!