In 2015, Crashlytics was named the top performance SDK and crossed over one million apps integrating our crash reporting SDK. But we didn’t want to stop there. In January, we were heads down enhancing Crashlytics and making it even more instrumental to how you build mobile apps.

Introducing the ability to log NSErrors

Crashes aren’t the only adverse events that can take place in a running app, where errors might occur in the background and affect their behavior or performance. In January, we were thrilled to officially release the ability to log NSErrors on iOS, OS X and tvOS. We wanted to empower you to optimize your user experience even when your app isn’t crashing.

We extended the #1 crash reporting experience so you can easily log and fix the most critical non-fatal errors on Apple devices — all in real time. You'll also notice we gave your issue list dashboard a complete visual refresh. Now, even looking at crashes can be an enjoyable experience :)

Enhancing Unity Support for Crashlytics

Building an amazing game can be one of the most challenging, yet invigorating experiences. We thought we could take the Crashlytics experience and bring it to your Unity projects right out of the box. Since announcing our beta support for Unity at Twitter Flight, we've seen overwhelming demand from many developers who are building some of the most cutting edge games. Starting today, we're opening up access to more beta testers.

Want to get your hands on it early? Sign up at Crashlytics Labs today — we'd love to hear what you think!

Here’s our internal changelog

Mac App and iOS SDK

• Added OS X support to Answers

• Gave the issue list dashboard a complete visual refresh

• Feature: Logging NSErrors is now out of Beta and ready to be used

• Fix: Correct a regression that can cause DWARF unwinding to fail for x86_64

• Fix: Correct a race condition that could happen when setting custom keys for the previous crash in the delegate callback method