> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/desktop-app/report-an-issue.md).

# Report an issue

**Report Issue** in the desktop app collects the logs, screenshots and device state support needs, and sends them.

{% hint style="info" %}
`Report Issue` — in the desktop app
{% endhint %}

|                    |                                                                                                      |
| ------------------ | ---------------------------------------------------------------------------------------------------- |
| **Platforms**      | macOS                                                                                                |
| **What it sends**  | Only platform related support, device and connection state. For testcase refernece mention thread ID |
| **When to use it** | Anything you can't explain from the run report and the troubleshooting table                         |
| **Why**            | Support gets the evidence immediately instead of asking for it tomorrow                              |
| **Watch out**      | Send it while the problem is fresh — the bundle carries *recent* logs, not all history               |

## Prerequisites

* Drizz desktop app installed and signed in
* The problem reproduced recently — the bundle carries recent logs only
* One line describing what you expected and what happened

## Check these first

These resolve most reports in under a minute.

1. Check the wallet badge. A vague server or availability error can be an exhausted balance.
2. Run **Help → Network Preflight**, especially if the same test worked on another network. See [Networks, proxies & preflight](/desktop-app/networks-and-preflight.md).
3. Open the before-screenshot of the failing step in report. A screen other than the expected one means the real failure is an earlier step.
4. Confirm you are on the current version. See [Updates & forced updates](/desktop-app/updates.md).

## Send a report

1. Reproduce the problem, or send the report during an occurrence.
2. Open **Report Issue** in the desktop app.
3. Write one specific line in the description field with Thread ID.
4. Submit. Drizz attaches the logs, screenshots and device state automatically — no manual attachment is required.

## What the bundle contains

| Included                        | Why support needs it                                                                        |
| ------------------------------- | ------------------------------------------------------------------------------------------- |
| **Application logs**            | What the app was doing at the moment it went wrong, including anything that failed silently |
| **Recent screenshots**          | What was actually on the device screen                                                      |
| **Device and connection state** | Which device, which platform, whether it was connected, what state it was in                |
| **App and environment details** | Your version, so support knows whether you're hitting something already fixed               |

The bundle carries **recent** logs and screenshots, not full history. Evidence from a problem hit three days earlier may have rolled off. For an intermittent problem, send the report on an occurrence.

## When to use it

| Situation                                                                                                                      | Use Report Issue |
| ------------------------------------------------------------------------------------------------------------------------------ | ---------------- |
| A run fails and neither the run report nor the [troubleshooting table](/reports-and-debugging/troubleshooting.md) explains why | ✅                |
| Sign-in completes but the app doesn't log you in, and relaunching didn't help                                                  | ✅                |
| A device shows up in `adb devices` or Xcode but not in Drizz                                                                   | ✅                |
| A step behaves differently from one run to the next with no change to the script                                               | ✅                |
| Anything hangs                                                                                                                 | ✅                |

## What to put in the description

The bundle carries the facts. The description carries the intent.

| Include                                | Example                                       |
| -------------------------------------- | --------------------------------------------- |
| What you expected to happen            | The cart screen opens                         |
| What happened instead                  | The tap fails as undoable                     |
| Which test and which step              | T04 step 7 — tap on Add to Cart               |
| Whether it's every run or intermittent | Every run since this morning                  |
| Which platform                         | Fails on the iOS simulator, passes on Android |

One line covering all five: `<Thread ID> T04 step 7 — tap on Add to Cart fails on the iOS simulator, passes on Android, every run since this morning`

## Common mistakes

| What you do                                              | What happens                                                         |
| -------------------------------------------------------- | -------------------------------------------------------------------- |
| Email a description of the symptom                       | Support asks for logs, and you lose a day to the round trip          |
| Use Report Issue three days after the problem            | The relevant logs may have rolled off. Do it while it's live         |
| Send the bundle with no description                      | Support has the evidence but not what you expected to see            |
| Photograph the error with your phone                     | The bundle already contains the real screenshots                     |
| Use it before checking your wallet balance               | A vague server error is often an empty wallet                        |
| Use it for a device problem before running `adb devices` | If adb can't see the device, Drizz can't either — and that's the fix |

## Next

* [Networks, proxies & preflight](/desktop-app/networks-and-preflight.md)
* [Troubleshooting](/reports-and-debugging/troubleshooting.md)
* [Updates & forced updates](/desktop-app/updates.md)

***

*Last updated: 6 August 2026*