Crash Reporting Callbacks

Covered here is how to set up the callbacks that fire before every crash report is sent so that a specific block of code is executed in your Android app.

Avoiding Memory Leaks

These APIs hold the callbacks in a strong reference, so we strongly suggest to avoid registering callbacks without unregistering them when needed, as it may cause a memory leak.

Before Sending a Report

This block is executed in the background before sending each report. You can use it to attach logs and extra data to reports.

Kotlin

Luciq.onReportSubmitHandler{report -> }

Java

Exporting Crash Metadata

You can use the below API to capture metadata about the crash including:

• Error Type: The error type including ANR (Foreground ANR), BG_ANR (Background ANR), Non-fatal errors and NDK crashes.
• Error Code: The specific error code associated with the crash.
• User Attributes: User attributes associated with the session.
• Error Description: The error message associated with the crash

Kotlin

CrashReporting.setOnCrashSentCallback { metadata ->
    Log.d("Luciq", "Crash sent error=${metadata.errorType} attrs=${metadata.userAttributes}")
}

Java