> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting/crash-reporting-callbacks.md).

# 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.

{% hint style="warning" %}

#### 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.
{% endhint %}

### Before Sending a Report

{% hint style="warning" %}
`Luciq.onReportSubmitHandler` is deprecated as of SDK version 19.14.0. Use `Luciq.setOnBeforeSendHandler`, available from 19.14.0, instead.
{% endhint %}

This handler runs in the background before each bug report and crash report is sent, including non-fatal errors, ANRs and fatal hangs. It doesn't run for NDK crashes, surveys, feature requests or chat replies. You can use it to add tags, user attributes, user data and file attachments to the report. Return the event you received to send the report. We recommend registering it when you build the SDK, so it also covers a crash from the previous app launch; see [Bug Reporting Callbacks](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-bug-reporting/bug-reporting-callbacks.md#before-sending-a-report).

{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}

```kotlin
Luciq.setOnBeforeSendHandler { event ->
    event.appendTags(listOf("checkout"))
    event.appendUserAttributes(mapOf("plan" to "premium"))
    event.setUserData("Cart: 3 items")
    // fileUri: a Uri your app can read
    event.addFileAttachment(fileUri, "cart.json")
    event
}
```

{% endcode %}
{% endtab %}

{% tab title="Java" %}
{% code overflow="wrap" %}

```java
Luciq.setOnBeforeSendHandler(event -> {
    event.appendTags(Arrays.asList("checkout"));
    event.appendUserAttributes(Collections.singletonMap("plan", "premium"));
    event.setUserData("Cart: 3 items");
    // fileUri: a Uri your app can read
    event.addFileAttachment(fileUri, "cart.json");
    return event;
});
```

{% endcode %}
{% endtab %}
{% endtabs %}

### Exporting Crash Metadata

{% hint style="warning" %}
`CrashReporting.setOnCrashSentCallback` is deprecated as of SDK version 19.14.0, with no replacement, and will be removed in an upcoming major release. Don't rely on it to confirm that a crash report was sent.
{% endhint %}

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

{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}

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

{% endcode %}
{% endtab %}

{% tab title="Java" %}
{% code overflow="wrap" %}

```java
CrashReporting.setOnCrashSentCallback(new OnCrashSentCallback() {
            @Override
            public void onCrashSent(@NotNull CrashMetadata crashMetaData) {
                
            }
        });
```

{% endcode %}
{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting/crash-reporting-callbacks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
