From Crashlytics Labs: Unity and tvOS Support, Logged Errors for iOS

by Jason St. Pierre, Product Manager

Last month, we improved our crash reporting service with enhanced visibility into the life cycle of an issue. Even though Crashlytics is already recognized as the #1 most implemented performance SDK, we knew there was more to do. Many app developers face challenges such as getting deep, actionable crash reports for their games, or gaining visibility into the stability issues that don’t always result in a crash.

Through Crashlytics Labs, we’re always tinkering with new ideas. Today, we’re announcing three new tools in beta: support for Unity, one of the most popular game development engines; support for tvOS; and the ability to log NSErrors on iOS, OS X and tvOS.

The onboarding process for Unity-based projects has traditionally been cumbersome. Our beta support for Unity aims to give you a completely streamlined onboarding experience. Right out of the box, our beta will support both Unity 4 and 5; you’ll no longer have to use your Mac app or Android IDE plugins to start building.

From our friends at Dots, Androidsx and Nordeus:

Having added a lot of plugins so far, I have to say that this was by far the easiest integration.

- Miša Damjanić, Game Designer,


We also knew that the developer community is excited to build tvOS apps that will live on Apple TV. Because of this, Crashlytics now supports crashes that come from those apps on Apple TVs. Available through Crashlytics Labs, you can now test out our tvOS app support in beta.

Beyond actionable insights into errors when an app or game crashes, we saw another need from many those who want visibility into NSErrors. Just because an app didn’t crash doesn’t necessarily mean that the user had a flawless experience, and our beta support for logging errors aims to help you solve that. Not all serious stability issues are crashes, and knowing about other non-fatal errors can help monitor and address problems before they become more serious, or uncover issues that might be due to a server/back end problem, etc. Starting in beta on iOS, OS X and tvOS, we plan to make NSErrors accessible so you have a way to optimize user experience even when your app isn’t crashing.

If you want to apply to test our new tools and other secret projects we’re working on, sign up here.

Cheers,