# Debugging

Since the widget runs within a webview in the mobile app, you can use the Chrome inspector on Android or Safari Web Inspector on iOS to debug. This allows you to view the console and inspect the HTML of the widget.

## Android Debugging

### Mobile

1. Plug in your mobile device.
2. Ensure USB debugging is enabled:\
   **Settings** → **System** → **Developer options** → enable **USB debugging**.

### PC

1. Open **Chrome** and navigate to `chrome://inspect/#devices` (or on **Edge**, use `edge://inspect/#devices`).
2. Under **Remote Target**, look for **"WebView in app.homey."**
3. Click **Inspect**.

## iOS Debugging

### Mobile

1. Plug in your mobile device.
2. Ensure USB debugging is enabled:\
   **Settings** → **System** → **About Phone** → **Developer options** → enable **USB debugging**.

### PC

1. Open **Safari** Settings, go to the **Advanced** tab, and enable the checkbox **"Show Develop menu in menu bar."**
2. In **Safari** , go to **Develop** → **\[device name]** → **\[app name]** → **\[url - title]**.

<figure><img src="/files/T2dVeHHYHdlfSW1ik8oV" alt=""><figcaption><p>Chrome Web Inspector</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://apps.developer.homey.app/the-basics/widgets/debugging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.