Mobile Crash Analytics & Reporting FAQ

Do I need a new SDK?

Crash Analytics requires Flurry iOS SDK version 7.8.0 or higher and Android version 6.7.0 or higher. If you are using an older version, you will need a new SDK.

What versions of Android are supported for Crash Analytics?

Proper re-symbolication of Android stack traces requires Flurry Android SDK 6.7.0 or greater.

But I use another Crash Analytics SDK.

If you are building an Android app, you can use as many Crash Reporting services as you like side by side, so you should not see any changes with your existing service.

For iOS apps, Apple only allows you to register one crash handler in your app at a time which means you can only run a single Crash Reporting service.

Our Crash Analytics feature is disabled by default, so if you are using another service and do not want to use Flurry Crash Analytics instead, you should leave it disabled and you will get the normal Flurry Analytics service without Crash. If you want to use Flurry Crash Analytics just enable it when you integrate the SDK.

Is the Crash Analytics enabled by default in the SDK?

It is enabled by default on Android, but disabled by default on iOS.

To enable Crash Reporting on iOS, place the following line of code before your call to startSession:

FlurrySessionBuilder *sessionBuilder = [[FlurrySessionBuilder new] withCrashReporting:YES];
[Flurry startSession:@"YOUR_API_KEY" withSessionBuilder:sessionBuilder];

In iOS, Flurry has disabled the Crash Reporting functionality to ensure that Flurry Crash Analytics feature does not affect the use of other crash reporting tools that might be in use by the application. When enabled, Flurry will collect crash reports and send it in the session data. The errors that are logged using the Flurry library will include stack traces that are captured at the point when the error is logged. Note that when this feature is enabled Flurry installs an uncaught exception handler and registers for signals.

We strongly recommend that developers do not install any uncaught exception handlers in their app if they enable this feature.

Is there an API to upload the dsym file so I could do it from my build process?

Yes, there is an API to let you upload the dsym file as part of your build process from the server, if you prefer.

I don’t see my crash after testing.

When a crash is encountered the crash reporter will collect the crash details as the app is crashing. However, the crash cannot be sent until the app relaunches. If you have intentionally caused a crash and do not see it, then make sure you are relaunching the app after the crash.

My question was not answered on this page.

Didn’t find what you were looking for? Check out the other options to get support.