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.*

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.*

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.*

Selecting objects from Game Screen Area

Problem: Select an object from Game Screen Area and no element is selected in the 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.*

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.*

Activating license while having a proxy running

Problem: Trying to activate a license for AltTester® Desktop fails if you have a proxy running because the request to altom.com might get blocked.

Workaround: 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.*

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.*