Known issues

Clickable area problems

Problem: Sometimes when opening the AltTester® Desktop app for the first time or when your display settings are changed, some of the UI elements in the application might become unresponsive to clicks, because their clickable areas are in a slightly different position than where the elements are actually rendered.

Workaround: Maximize or resize the application window.

Affects: AltTester® Desktop 2.0.*, 2.1.*, 2.2.*, 2.3.*, 2.4.*

Sometimes the tap action is recorded, but not reflected in the application

Problem: Sometimes the tap action is recorded, but not reflected in the application. (Make sure that the click on object option is checked)

Affects: AltTester® Desktop 2.0.*, 2.1.*, 2.2.*, 2.3.*, 2.4.*

Problem with reverse port forwarding for iOS

Problem: Reverse port forwarding is not working for iOS devices.

Workaround: Set the iOS device as a personal hotspot, enable Hotspot via USB on the machine running the AltTester® Server and add the IP of the machine running the AltTester® Server to the first input field in the green popup from the instrumented app/game. Find more details here

Affects: AltTester® Desktop 2.0.*, 2.1.*, 2.2.*, 2.3.*, 2.4.*

Selecting objects from the Screenshot area

Problem: Select an object from the Screenshot area and no element is selected in Objects Hierarchy area.

Workaround: The issue happens when the scenes are not included in the build when instrumenting your game with AltTester® Unity SDK.

Affects: AltUnity Inspector 1.0.0-1.4.0, AltTester® Desktop 1.5.0-2.0.*, 2.1.*, 2.2.*, 2.3.*, 2.4.*

Using Unity as a Library

Problem: Exporting your game as a library (Unity as a Library) and adding native elements to it might break the connection between the game and the Inspector.

Affects: AltUnity Inspector 1.0.0-1.4.0, AltTester® Desktop 1.5.0-2.0.*, 2.1.*, 2.2.*, 2.3.*, 2.4.*

Activating license while having a proxy running

Problem: AltTester® Desktop and the AltTester® Server both need to reach mid.alttester.com to check the internet connection and activate the license. If a proxy blocks that host, AltTester® Desktop shows Please check your internet connection and try again and the server is not started. A proxy that passes this traffic through does not interfere.

Workaround: Allow mid.alttester.com and alttester.com through the proxy, or use AltTester® Desktop with a setup that doesn’t have a proxy running.

Affects: AltUnity Inspector 1.0.0-1.4.0, AltTester® Desktop 1.5.0-2.0.*, 2.1.*, 2.2.*, 2.3.*, 2.4.*

Recording: Assert fails if string contains new line

Problem: Trying to record a test that is checking a string that contains a new line might fail because a different new line character is applied

Workaround: Change the file settings for new line format from CRLF to LF

Affects: AltTester® Desktop 2.0.*, 2.1.*, 2.2.*, 2.3.*, 2.4.*

AltTester® Desktop input action is still reflected in the app when AltTester® Input toggle is unchecked

Problem: Input actions can be performed through Unity’s Input class or through the Event System. When checking or unchecking the AltTester® Input toggle, it only affects the actions done through the Input class. As a result, even if the toggle is unchecked it might happen that the interaction with the app performed within the AltTester® Desktop is still reflected in the app.

Affects: AltTester® Desktop 2.0.*, 2.1.*, 2.2.*, 2.3.*, 2.4.*

Load additive not working for Unreal apps

Problem: If your app is instrumented with AltTester® Unreal SDK 1.1.0 or lower, loading scenes additively won’t be available in the AltTester® Desktop.

Affects: AltTester® Desktop 2.2.*, 2.3.*

Fatal error: Cannot access a disposed object ‘System.Net.Sockets.NetworkStream’

Problem: While running tests, the app unexpectedly disconnects from AltTester® Server and a [Fatal] Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'. error is logged. This happens due to a race condition when the server attempts to send data to a client that has recently disconnected, often triggered by a “reconnection storm” from older versions of the C# Bindings.

Workaround: Update your C# Bindings to version 2.3.1 or higher. This version includes a fix that stabilizes the connection and prevents the reconnection loops that trigger this error.

Affects: AltTester® Desktop 2.3.1 (when used with C# Bindings < 2.3.1)