Introducing Velocity Alerts

by Jason St. Pierre, Product Manager

Since the birth of Crashlytics, our passion has always been to help you fix the most prevalent issues quickly and painlessly. Just last month, we released badges to help you hone in on crashes that stand out against the rest.

Today, we’re thrilled to introduce Velocity Alerts: intelligent, proactive alerting on the most critical issues happening in your app. Now, you truly know when you need to take action right away.

Powered by the #1 mobile analytics solution

While our system already distills and prioritizes your crashes based on their impact, there was more we could do to make your life even easier. By combining your app’s crash data with usage analytics from Answers, our new Velocity Alerts enable you to triage unexpected, high-impact issues with minimal effort.

Now, once you’ve enabled Answers as part of Crashlytics, our system will proactively check to see if there is a statistically significant number of sessions that have ended due to a crash related to one issue on a particular build. If so, we'll let you know if that issue is a hot patch candidate and needs your attention immediately right on your dashboard. You’ll also get an email alert in your inbox as well as a push notification if you’re using the Fabric mobile app(Android support coming soon). With Crashlytics, you’ll never miss a critical bug!

While at it, we’ve also redesigned all of our notification emails so important information are even more clear and actionable.

We couldn’t be happier to release this so you can sit back, relax and just focus on building the best app. If you’re already using Crashlytics with Answers, Velocity Alerts are automatically enabled for you. If not, get started with Answers!

Get Velocity Alerts

Crashlytics January Update

by Brian Lynn, Sr. Product Marketing Manager

img.png

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 tvOSWe 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 ourbeta 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

Introducing the ability to log NSErrors

by Jason St. Pierre, Product Manager

At last year’s Flight conference, we opened beta access to one of our new tools at Crashlytics Labs: the ability to log NSErrors on iOS, OS X, and tvOS. Beyond actionable insights into errors when an app or game crashes, we wanted to empower you to optimize your user experience even when your app isn’t crashing. Since Flight, we’ve been building this out, while releasing other major features such as Crashlytics for tvOS along the way.

Kicking off the new year strong, we’re excited to share today that we’re officially releasing the ability to log NSErrors on iOS, OS X and tvOS with Crashlytics!

Total Visibility Beyond Crashes

Crashes aren't the only adverse events that can take place in a running app. Errors might occur in the background and affect the behavior or performance while the app is running, leading to poor user experience or other serious problems later. Knowing about these non-fatal errors can help you monitor and address problems before they become more serious, or uncover issues that might be due to a server/back end problem.

With Crashlytics, we’ve 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. Just like for crashes, you’ll have everything you need: in-depth stack traces, cross version analysis, device/OS breakdowns, among all the other features you already know. 

To get started with the new feature, simply go to your Crashlytics dashboard and select the “Non-Fatals” filter option. Now, all your non-fatal errors will be grouped by their error domain and code, and you'll see the NSLocalizedDescription right there in the list. 

We couldn’t be happier to get this new feature into your hands and look forward to the awesome apps you’ll be building this year. Happy coding!

Introducing Crashlytics for tvOS

by Jason St. Pierre, Product Manager

Last month at Flight, we opened beta access to our crash reporting for tvOS project at Crashlytics Labs. Since then we’ve received much positive feedback from many of you. Today, just a month after Flight, we’re thrilled to share that we’re officially releasing Crashlytics for tvOS!

The #1 Crash Reporting Solution Now on Apple TV

Our passion has always been to deliver the most powerful developer tools. With Crashlytics, we’re solving the biggest challenges in crash reporting for iOS and Android; but we didn’t stop there. Many of you are building apps for TV today, and we’re excited to support the next generation of experience you’re crafting for the living room, starting with Apple TV.

Our tvOS support gives you the same award-winning experience that you’ve come to expect from us, starting with prioritizing your most prevalent crashes down to giving you the exact line of code that caused your Apple TV app to crash. Just like on iOS, there’s no need to wait days for a crash report: we’ll notify you with what’s important in real time so you can fix crashes as they happen. On top of that, you’ll have total visibility into an issue’s life cycle for your Apple TV apps, with a complete picture of how an issue is affecting your builds.

Don’t take our word for it:

Our team is building the next generation of experiences for our users on devices like the Apple TV. The Crashlytics team has done it again. They've brought the same crash reporting tool that we love to Apple TV and it's going to be instrumental for us moving forward.

- Ryan Poolos, CEO


MobilityWare is excited about the upcoming launch of our Solitaire and Blackjack titles on Apple TV. Crashlytics was essential in creating a stable and bug free game. Their SDK quickly integrated into our games taking just minutes to replace the iOS version with the tvOS version. Awesome job!

- Jeffrey Hohenstein, Dir. of Engineering


Beyond tvOS: Enhanced Notifications for Beta on Android

While the foliage is in full form, we also spent November finding new ways to enhance the Crashlytics experience. We realize how important it is to get timely notifications to your users.

That’s why, on top of tvOS support, we’ve enhanced our notification functionality for your beta release process on Android. Now, your testers will be notified about your latest builds much faster, via push.

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,