> ## Documentation Index
> Fetch the complete documentation index at: https://dragonwingdocs.qualcomm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Known Issues

> Current limitations and workarounds for the Qualcomm® VSCode Extension.

The table below lists confirmed issues with the current release and recommended workarounds.

| Issue                                                               | Workaround                                                                            |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| YOLO models are not downloaded by the IDE                           | Download them manually to `/etc/models` on the target device                          |
| Extension does not work with the VS Code **Snap** package on Ubuntu | Install the `.deb` package — see [Install VS Code on Ubuntu](../setup/install-vscode) |
| Dev kits may ship with outdated firmware                            | Flash the latest image using the [Getting Started wizard](../quick-start)             |
| Post-flash initialization script not run automatically              | After flashing, run **Dashboard → SDK → Configure Device**                            |
| Rubik Pi with QLI 1.3 or older requires additional UFS provisioning | Complete the UFS provisioning step **outside** the IDE before using the extension     |
| Limited testing on macOS / UTM environments                         | Use Ubuntu 22.04 or Windows + WSL for the best experience                             |
| Limited testing on Ubuntu 24.04 hosts                               | Ubuntu 22.04 is the recommended and fully tested host                                 |

<Note>
  For devices on Qualcomm Linux software version **1.3 or older**, additional UFS provisioning and CDT programming steps are required outside the IDE. Refer to the [Qualcomm Developer documentation](https://developer.qualcomm.com) for these steps.
</Note>
