> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-agent-android-guide/8.0/troubleshooting.md).

# Troubleshooting

Learn how to troubleshoot Cortex XDR agent app for Android.

Use the following resources to troubleshoot Cortex XDR agent app for Android:

* Report an issue with the Cortex XDR agent app.

  To report an issue with the Cortex XDR agent app, your Support contact may ask you to collect relevant version information and send logs. When you use the Report a Problem feature, Cortex XDR collects the relevant version information and logs and attaches them to a message in the messaging application of your choice, in order to send it to your Support contact.

  1. From the home page, open the menu at the top left, and tap Settings → **Logs and Reports**.
  2. **Report a Problem**, and then select a messaging app.
  3. Select the desired recipient, provide additional details to help support understand the issue or problem that you encountered, and then send the message. The zip file is automatically attached, and sent with the message.
* View the Cortex XDR app version and policy version.
  * From the home page, open the menu at the top left, and tap **About**.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xdr-agent-android-guide/8.0/troubleshooting.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.