Known issues
Problem starting AltTester® Desktop from batchmode on MacOS due to name change
Problem: It is possible on some CI pipelines that the server cannot be started (and no error shown in the pipeline) if an AltTester® Desktop version < 2.1.1 is installed prior to running the pipeline again and there is a newer Desktop version available. This resides from the fact that when the pipeline script downloads the newer version from the website (which always takes the latest version) the executable file name is changed (as a space was removed - instead of AltTester Desktop
now it is named AltTesterDesktop
).
Workaround: Use the updated executable name when starting the batchmode script - more details in this section
Affects: AltTester® Desktop 2.1.1 and higher if earlier than the 2.1.1 version was already installed
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 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.*
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.*