The most powerful, yet lightest weight crash reporting solution for iOS and Android developers. | Crashlytics
Fabric Logo

Looking to integrate award winning Crashlytics into your app? Crashlytics, Beta by Crashlytics, and Answers by Crashlytics are now part of Fabric, the easiest way to build the best apps. Learn more about Fabric here.

Poweful yet lightweight

Crashlytics for Android delivers deep, rich crash reporting across devices in real-­time. Crashlytics performs a detailed analysis of every thread on every Android device to identify the most important issues.

We’re obsessed with making developing apps as easy as possible. Crashlytics for Android Studio, Eclipse and IntelliJ gives you instant reports right in your workplace environment.

Our plugin keeps you informed of the issues within your app so you can track the most prevalent crashes without leaving your IDE.

The Crashlytics SDK works seamlessly across all devices, versions (even the outdated ones) and from all types of apps -­-­ from widgets to wallpapers to your favorite gaming apps.

Crashlytics SDK. Capture what you need in real-time.
Uncaught icon
Uncaught Exception Reporting

When your app throws an uncaught exception, Crashlytics quickly records the stack trace and state of the device at the time the exception was thrown and sends the crash information to our servers for processing. You get complete visibility for every crash, effortlessly.

Caught icon
Caught exception reporting

Crashlytics isn't just for uncaught exceptions! Adding a single line of code in your catch block will report caught exceptions to Crashlytics for processing, and you are still free to handle the exception however is best for your users. You get the full stack trace and all the same device information we collect for fatal crashes, so you can identify and fix bugs even if your app doesn't crash!

Automated icon
Fully automated deobfuscation

We automate deobfuscation of ProGuarded stack traces for apps built using our ant tools, maven tools or IDE plugins. We did the legwork for you. Built into your existing workflow, our SDK will have negligible impact on your app.

On device exception handling Server side Analytics and Deobfuscation Highest fidelity report

The Crashlytics SDK uses a multi-­step process to analyze your crashes and automatically deobfuscates stack traces. We start with on-­device exception handling.

Once a crash report makes it into our system, stack frames are then re-­processed against your application’s mapping file that was automatically uploaded to our servers at build time.

This process, coupled with our advanced aggregation algorithms, provides the highest information fidelity available.

The Crashlytics SDK was designed with the utmost care to guarantee that
it has no negative impact on your app’s performance:

On average, Crashlytics adds less than the size of a single image to the weight of your application.

We don't require linking against any additional frameworks or libraries.

When initialized at start-up, Crashlytics performs only a minimal amount of required work and defers the rest until a few seconds after app startup completes. This delay time is configurable -- we want your app to start as quickly as possible!

Our memory footprint has been carefully tuned to be the minimum necessary.

We care tremendously about the stability of your app and the experience for your users. If for any reason our SDK fails to do what it's supposed to do, it has no impact on your app or to your users.

We use run-time feature detection to ensure compatibility with version 2.1 and beyond.

Our exception handler waits silently until an uncaught exception is thrown. We process the crash quickly and efficiently before returning control to the Android runtime, with no noticeable impact on your app’s performance. Your users will never know we’re there!

When the device is in airplane mode or experiencing a bad network connection, we will queue the crash reports so you still see every crash - with no impact on your app's performance.

! Oops! There's been an error. Try again!