F.2 Init Crash

Crash is now deprecated. Use Firebase Crashlytics instead.

Initialize Firebase Crash

firebaseCrash.ane is automatically initialized as soon as your implement the ANE and its dependencies/Frameworks.

Firebase Crash Reporting creates detailed reports of the errors in your app. Errors are grouped into clusters of similar stack traces, and triaged by the severity of impact on your users. In addition to automatic reports, you can log custom events to help capture the steps leading up to a crash.

Create custom logs

You can use this ANE to log custom events in your error reports. If you wish to log an event you only need to pass a string as the argument to log(), as shown in this example:

import com.myflashlab.air.extensions.firebase.crash.*;

Crash.log("my log msg");

Create your first error

Firebase Crash Reporting automatically generates reports for fatal errors (or uncaught exceptions). However, for you to be able to test the reporting, you can manually create a crash in your app and see the results in your Firebase Console in one or two minutes.

Crash.crash();

When calling the crash(), your iOS app will be forced closed! This behavior is to simulate a crash in your app/game. However, this will not force close your app on the Android side but it does initialize the crash reporting process.

When testing the ANE on iOS, you should notice that the crash report initiated by the crash() method will not be uploaded to Firebase console unless you run the app again. On our tests, we noticed that the report is generated only if you run the app again without connecting it to the AIR debugger!