Known Issues - Squish 8.0.0 Release¶

Release Date: Jul 1st, 2024

Recommended Update: 8.1.0

Squish for Qt¶

Cannot build Squish for Qt with Qt >= 6.7.2¶

When building Squish for Qt from sources, squishidl generates script bindings for Qt. With Qt 6.7.2, std::chrono templates are used that are not correctly expanded by squishidl which causes the build to fail.

Cannot run Ruby test suites with 32-bit packages on Windows 11¶

Please check the corresponding entry in the 7.2.1 known issues page .

Look-up and picking of QtQuick objects with image fails¶

Due to a regression, look-up of QtQuick items/objects containing source property (e.g. Image ) does not work in Squish 8.0.0. This may cause existing test scripts to fail with Object Not Found errors. Picking of these objects in the Squish IDE is not possible either.

Solution: Please contact our technical support to obtain a Squish package with a fix. (Fixed on 2024-08-07)

Applications based on Qt < 5.1 & MinGW fail to launch¶

The Runner/Server Log view in the Squish IDE contains...

Resolving symbol '_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent' failed: The specified procedure could not be found.

...(or a translated variation of this) after Squish tried and failed to launch the application.

Solution: Please contact our technical support to obtain a Squish package with a fix. (Fixed on 2024-10-23, SQUISH-18200)

Workaround: This is a regression that has been introduced in 8.0.0. Using 7.2.1 may be an alternative/workaround.

Squish for Web¶

Squish extension for Chrome automatically uninstalled/disabled with Chrome 132 or newer¶

See the dedicated page for this known issue affecting all Squish versions prior to 8.1.0 .

Squish for Android¶

Squish reports timeout on initial hookup (starting a recording/replaying) on Android-34 emulator¶

At the time of the initial hookup (when starting a recording/replaying), the AUT starts, but Squish reports a timeout.

Workaround:

Try enabling 'JWDP' in the emulator (see JWDP options ) (execute this command in a shell/command prompt; specify the option '-d device_id_here' in case of multiple Android devices):

adb shell setprop persist.debug.dalvik.vm.jdwp.enabled 1

Then reboot the emulator and try again.

If the problem persists, please contact our technical support .