L.2 Test Implementation

Force a crash to test your implementation

You don't have to wait for a crash to know that Crashlytics is working. You can use the SDK to force a crash. Create a button in your app and when it's hit, simply call Crashlytics.crash();

Note: Your app will shut down when the crash happens. So you need to re-run your app again so Crashlytics SDK can initialize again and find the chance to send the crash report to Firebase console.

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

/*
    First initialize FirebaseCore. You cannot use ANY of Firebase children unless
    you have already initialized FirebaseCore successfuly.
*/

// Initialize Crashlytics anytime after a successful Firebase initialization.
Crashlytics.init();

// Force a crash after 10 seconds, just a test!
setTimeout(toCrash, 10000);
function toCrash():void
{
    Crashlytics.crash();
}

Enable Crashlytics debug mode

If your forced crash didn't crash, crashed before you wanted it to, or you're experiencing some other issue with Crashlytics, you can enable Crashlytics debug mode to track down the problem. When you do that, you should use AndroidStudio logcat window or xcode debug console window to see the SDK debug logs.

When releasing your app, make sure the debug mode is off.

// pass true when initializeing the ANE and the debug mode will be on
Crashlytics.init(true);