Known Issues - Squish 9.2.1 Release¶
(Known Issues of previous version)
Release Date: March 19th, 2026
Recommended Update: n/a
Squish for VNC¶
On macOS, Squish for VNC hangs when connecting to a remote VNC server running Apple Remote Desktop (ARD)¶
When attempting to connect to a remote VNC server running ARD in order to record or replay a test case, Squish for VNC
hangs on macOS. In Squish IDE, a dialog with an infinite progress bar and a message Launching application '_squish_vncaut'
is shown. The dialog can be closed, but the connection to the remote VNC server will never be established. This renders
recording and test case execution unusable.
The problem is limited to this specific set-up (macOS client connecting to macOS ARD server). Other combinations (Windows or Linux client connecting to macOS ARD server, macOS client connecting to Linux VNC server,...) worked reliably in our testing. The issue is caused by incompatibility between Squish's use of cryptographic libraries and LibreSSL as shipped by Apple.
Workaround
Note: Use of OpenSSL 1.1 is deprecated and it has not received security updates since Sep 2023. We strongly recommend using this workaround only in secure environments when there's no other alternative.
- Install OpenSSL 1.1 via Homebrew:
brew install rbenv/tap/openssl@1.1- OpenSSL 1.1 is not part of the official packages for Homebrew
- Ruby Devevelopers still provide this tap to allow use of older Ruby, see the tap's project page for more details
- Ensure OpenSSL 1.1 is preferred over the System LibreSSL
- in a terminal session do:
export DYLD_LIBRARY_PATH=/opt/homebrew/opt/openssl@1.1/lib:$DYLD_LIBRARY_PATH - this environment needs to be active for the squishserver being used to launch with Squish for VNC
- Use
/usr/local/opt/openssl@1.1/libinstead on Intel-based Mac's
- in a terminal session do:
- Ensure squishserver inherits this environment, all following commands must be started from the same terminal session
- Start a squishserver explicitly, for use with a squishrunner or the IDE:
bin/squishserver - Run a testsuite from the commandline with auto-starting squishserver:
bin/squishrunner --testsuite suite_your_vnc_tests --local ... - Start the IDE from the terminal to use the squishserver it automatically starts:
open squishide.app
- Start a squishserver explicitly, for use with a squishrunner or the IDE:
Installation¶
Installation of Squish fails on Windows if user profile name contains non-ASCII characters¶
On Windows, users with non-ASCII characters in their user profile name (i.e. their home directory will look something like
C:\Users\Jürgen) may be unable to install Squish from binary packages.
The first symptom of the problem is visible in the second step of installation (configuring license), where the Qt License Server
option is not available. Even if one of the remaining licensing options (license key or Floating License Server) is selected,
the installation will likely fail later, as several installer components cannot drop files into a temporary folder (which in the example
above would look like C:\Users\Jürgen\AppData\Local\Temp) with non-ASCII characters in the path.
Workaround
Two possible workarounds (changing paths and modifying ANSI codepage system settings) are documented in detail in the article IDE does not start or shows errors when installed in paths with non-ASCII characters
Unattended Squish installation with Floating License Server (FLS) fails for the user that had Qt License Server (QLS) configured before¶
Unattended (non-interactive) installation
with FLS address provided
on the command-line (--license-server-floating option) fails if Squish was previously installed for the current user and configured
with QLS. The following error message is shown: Configuring with Squish Floating License Server (FLS) address ... Error: Invalid telemetry value: Specify 'telemetry=1' or 'telemetry=0', to enable or disable telemetry.
Workaround
Find a hidden file named .squish-license in user's home directory and delete it. Then proceed with unattended installation as usual.