Known Issues - Squish 9.1.0 Release¶
(Known Issues of previous version)
Release Date: August 11th, 2025
Recommended Update: n/a
Scripting¶
pip is missing from the Python 3.10 bundled with Squish binary packages¶
pip, a package manager for Python, is mistakenly not included in the Python 3.10 bundled with binary packages of all
Squish editions. Using the Python interpreter that ships with Squish to install/manage external Python modules with pip
(e.g. from the Squish IDE) is therefore going to fail, with an error message such as pip not installed or not found in interpreter.
Workaround 1
Install pip manually using the Python interpreter bundled with Squish.
On Linux:cd $(SQUISH)/python/bin
./python -m ensurepip --default-pip
On macOS:cd $(SQUISH)/python/Python.framework/Versions/3.10/bin
./python -m ensurepip --default-pip
On Windows:cd $(SQUISH)\python
python.exe -m ensurepip --default-pip
Workaround 2
Configure Squish to use an external Python interpreter that contains a working pip. Read
squishconfig documentation
to find out how to do it.
Squish for Qt Quick Ultralite (QUL)¶
Problems with detecting, flashing, and resetting Espressif ESP32 MCU devices on Linux¶
Starting with Squish 9.1.0, automated testing of applications written with Qt Quick Ultralite 2.11 or newer
is possible on a new family of MCU devices: Espressif ESP32. On some Linux distributions, additional permissions
(access to USB and serial port) need to be set to prepare the MCU device for testing with Squish. Without these
permissions, the device will be detected only as a generic UART device by the Squish IDE (if detected correctly,
the device identifier will contain esp-idf or ESP-IDF string). Consequently, flashing and resetting the device
will fail. This failure is usually visible in squishrunner log as Raw UART connection cannot flash a new image to the device
or Raw UART connection cannot reset the device.
The easiest way to set the right permissions to access USB and serial port is to use vendor-provided udev rules as outlined in platform-specific instructions in ESP-IDF programming guide .
Cannot configure paths to STM32 vendor tools in the Squish IDE¶
At the moment, it is not possible to configure paths to STM32 vendor tools in the server settings GUI of the Squish IDE (Edit → Preferences → Server Settings → MCU Settings). Even if configured paths point to a valid MCU vendor tools installation on the disk, they are evaluated as invalid by the IDE. As a result, a warning icon appears next to the MCU Settings and changes to the configuration cannot be saved, as the OK button in the preferences dialog remains inactive.
Solution
Please contact Squish technical support to obtain a Squish snapshot package with a fix for this issue (SQUISH-19744)
Workaround
Use the command-line interface of squishrunner to configure access to the vendor tools:
cd $(SQUISH)/bin
squishrunner --config mcuSettings St-Link:Programmer=/path/to/STM32CubeProgrammer/bin/STM32_Programmer_CLI[.exe]
squishrunner --config mcuSettings St-Link:GDBServer=/path/to/STLink-gdb-server/bin/ST-LINK_gdbserver[.exe]