We spent February refining our dashboard and thinking about ways we can enhance the Crashlytics experience that many of you have come to know and love. In the last few months, we shipped the ability to log the most critical non-fatal errors on iOS apps as well as a complete visual refresh to the dashboard.

This month, we reexamined the behaviors of alerting and noticed opportunities where we could make your time spent on crashes even more efficient. We're excited to introduce a new way to highlight significant and unique bits of information about particular issues with badges!

The most powerful and intelligent crash reporter

Many crashes often have a common characteristic. For example, a number of issues may have all been related to crashes on a particular device model. With this new feature, we wanted to make triaging your crashes even more efficient on Crashlytics.

With this feature, we highlight when particular pieces of information are significant for an issue and call them out with badges on the dashboard.

After a new release, you'll easily be able to identify if you have any issues that stand out against the rest. For example, you can stop ignoring top issues if they are only prevalent on jailbroken devices, or you can quickly react to problems caused by the latest OS release. With this new feature, you’ll be able to triage many issues like these at a glance.

We were thrilled to hear the positive feedback from many of you!

Now on the Fabric mobile app

Last week, the Fabric team launched the new Fabric mobile app and the Crashlytics badging feature is just one of the many insightful things we’ve integrated with the app. Using the Fabric mobile app, you’ll get push notifications about what matters most: full stacktraces, number of affected users, and breakdown of devices and platforms – all in real time. This way, even before you open your laptop, you know where to look for a bug, who to reach out to on your team, and how it could affect your metrics.

We’ll be shipping even more enhancements in the coming months — stay tuned for more!

Here’s our internal changelog:

Mac App and iOS SDK

• Fix: Improved stability when running on OS X 10.7.

• Fix: Correct a rare case where libz may fail to compress crash reports before submitting. Previously we would drop the report, now we fall back to sending an uncompressed version.

• Enhancement: Implemented retry logic to handle partial success from the write syscall. This should help address an extremely rare case of report data corruption.

Web

• Added issues badges to dashboard. 

Integrations

• Integrated with Fabric mobile app on both iOS and Android.