> 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/kmp/setup-luciq-for-kmp/setup-crash-reporting/symbolication-deobfuscation.md).

# Symbolication/Deobfuscation

Make KMP crash stack traces readable. The native SDK handles symbolication, and Android also needs a ProGuard or R8 mapping file for each build.

Crash reports need symbolication (native stack traces) and, on Android, deobfuscation (ProGuard/R8 mapping) to be readable. The KMP library forwards crashes to the native Luciq SDK; symbolication and deobfuscation are handled by the **native** SDK and the Luciq dashboard.

### Android

* **ProGuard/R8**: Upload your mapping file when you upload a build to the Luciq dashboard (or configure your CI to do so). The dashboard uses it to deobfuscate stack traces.
* **NDK**: If you use NDK crash reporting, ensure native debug symbols (or symbol upload) are configured as required by the native Luciq Android SDK.

There is no KMP-specific API for mapping files; follow the [Luciq Android documentation](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting/deobfuscation-for-android) for your build setup.

### iOS

* **dSYM**: Upload dSYMs for your app so the dashboard can symbolicate iOS crash reports. This is usually done via the Luciq dashboard or your CI when you upload a build.

The KMP library does not change how symbolication works; it uses the native Luciq iOS SDK. Refer to the [Luciq iOS documentation](https://docs.luciq.ai/ios/setup-luciq-for-ios/setup-crash-reporting/symbolication) for dSYM upload and settings.


---

# 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/kmp/setup-luciq-for-kmp/setup-crash-reporting/symbolication-deobfuscation.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.