> 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-bug-reporting.md).

# Set up Bug Reporting

Set up Bug Reporting and feedback in your Android app. Covers integrating the SDK, showing it to users, and the prompt options they choose from.

{% hint style="info" %}

### Integrating and Showing Luciq

To be able to use Luciq's Bug Reporting and Feedback product, you must first [integrate the SDK](https://docs.luciq.ai/android/set-up-luciq-for-android/integrate-luciq-on-android.md). You should also understand how to [show the SDK](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-bug-reporting/showing-luciq.md).
{% endhint %}

Your users and beta testers can show Luciq Bug Reporting from any page in your app. When they select "Report a bug", "Suggest an improvement", or "Ask a question" from the default [Prompt Options](https://docs.luciq.ai/android/set-up-luciq-for-android/sdk-customizations/prompt-options.md) menu that pops up when they show Luciq, these reports are sent to the bugs page of your dashboard with all the information and logs you need to pinpoint any issues.


---

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