Release notes#

What changed in each release of AltTester® Unity SDK since 2.2.0. For the steps to take when you upgrade, see the upgrade guides. Every release, with its downloads, is also on GitHub.

Version 2.4.1#

Released 12 November 2026.

Fixes#

  • The drivers (C#, Java, Python and Robot Framework) close the connection when connecting or the server version check fails. Before, a failed attempt could leave the connection open, and the driver couldn’t reconnect to an iOS app after the app was reset.

Version 2.4.0#

Released 5 November 2026. See the upgrade guide.

Before you upgrade#

  • Delete Assets/AltTester before you import the new .unitypackage. The AltTester® assemblies moved to new folders, so importing over the old version leaves duplicate assemblies. Your Editor settings in Assets/Plugins/AltTester are kept. If you installed through OpenUPM, you don’t need to do anything.

  • You no longer need the TMP_PRESENT define. AltTester® now detects TextMeshPro at runtime, so you can remove the define from Player Settings and from your custom build scripts.

  • The log prefix changed from |Tester| to |AltTester|. Update any log filters or parsers that match the old prefix.

  • ServerLogManager is now called AltTesterLogManager. Rename it in any code that references it.

New features and improvements#

  • Unity 6.5 support.

  • Touch data matches a real device on the legacy Input Manager. Taps and BeginTouch/MoveTouch/EndTouch now report correct tapCount, deltaTime, deltaPosition and Stationary phases. Each phase lasts exactly one frame, and the touch is applied before your scripts’ Update() runs. Custom input code that polls Input.touches no longer sees a touch begin twice.

  • Input.GetKey/GetKeyDown/GetKeyUp(string) accept Unity key names such as "space", "left shift" and "[1]". Before, these threw an exception every frame while a driver was connected.

  • Production builds stay clean. The iOS post-process, the native plugins, the input axes and the extra link.xml code now apply to instrumented builds only.

  • Opening the AltTester® Editor window no longer changes Player Settings. Only Build, Build & Run and Play in Editor add the ALTTESTER define. Builds made from Unity’s Build Settings or Build Profiles are no longer instrumented by accident.

  • The AltTester® prefab is removed after a build even when the Editor window is closed, including command-line builds. Custom build methods can call the new AltBuilder.RemoveAltTesterFromScene.

  • Release builds log why AltTester® doesn’t start. Before, it failed silently.

Fixes#

Builds and the Editor

  • Managed Stripping Level Low, Medium and High no longer strip the AltTester® code, so apps built with those levels can be driven again. Dedicated Server builds are now detected as instrumented.

  • A stale or broken AltTester® prefab is regenerated in place, keeping its GUID and scene references. This also works in -batchmode -quit builds.

  • The Editor no longer adds a second AltTester® prefab when the scene already has one, and it keeps prefabs you placed by hand.

  • Changes in the AltTester® Editor window are saved on File → Save Project. Before, they could be lost after a restart.

  • A failed instrumented build no longer leaves an input axes file or an empty Assets/Resources folder behind.

  • An Editor build with an Untitled scene open no longer fails with Scene file not found: ''.

  • Fixed a NullReferenceException in the AltTester® Editor window, and one in the log viewer when the prefab is instantiated at runtime.

  • Removed a “Creating touch at…” warning that was logged for every simulated touch.

Connection

  • The connection panel shows “disconnected” when the server becomes unreachable, for example when its network is cut. Before, it could keep showing “Connected”.

  • A protocol mismatch (WS vs. WSS) now shows the wrong-protocol error instead of staying on “Waiting to connect”. The error is no longer shown by mistake when you use adb reverse and no server is running.

  • Minimising and restoring the app no longer throws InvalidOperationException: The current state of the connection is not Open.

  • An app in the background now reports its paused state when it connects, so it no longer disappears from the connected apps.

  • Fixed frame stutters caused by the keep-alive check running on the main thread.

Bindings

  • C#: fixed race conditions and message ID collisions that could cause flaky command responses.

  • Python: notification callbacks added with overwrite=True are now called once instead of repeatedly.

  • Robot Framework: the driver now reports itself as a Robot driver.

Version 2.3.2#

Released 11 June 2026. No release notes were published for this version; see its changes on GitHub.

Version 2.3.1-hotfix.1#

Released 9 April 2026. No release notes were published for this version; see its changes on GitHub.

Version 2.3.1#

Released 2 April 2026.

  • Improved performance and behaviour of the green pop-up.

  • Improved finding objects by text.

  • The Tap command works on UI Toolkit elements. Non-GPL

  • Fixed issues with the notification commands.

  • Fixed a WebSocket error in apps running in the Unity Editor.

  • Fixed connection issues with BrowserStack on devices running iOS 16 and newer.

Version 2.3.0#

Released 28 January 2026.

New features and improvements#

  • Unity 6 support.

  • A new secureMode parameter for AltDriver. See Secure mode (WSS).

  • More AltDriver constructors in the Java driver.

  • Updated support for the New Input System.

Fixes#

  • WebGL: fixed the “red popup” message and wrong protocol error messages, and improved probing in the WebGL WebSocket client.

  • iOS: fixed a dependency issue with location usage descriptions.

  • Android: fixed a runtime error.

  • Fixed the green pop-up display.

  • Fixed platform switching in the AltTester® Editor window.

  • Prevented cases where files could be deleted by accident.

  • Fixed issues with the Event System.

  • Improved the handling of protocol mismatch errors.

  • AltConsoleLogViewer finds the AltTester® prefab at runtime, which makes it more robust.

Dependencies#

  • Updated AltWebSocketSharp to version 1.0.8.

  • The Robot Framework requirement is no longer pinned to one version.

  • Added missing Unity module dependencies.

Version 2.2.7#

Released 4 December 2025. No release notes were published for this version; see its changes on GitHub.

Version 2.2.6#

Released 25 November 2025.

Main changes#

  • The input simulation (both the old Input Manager and the New Input System) was reworked. This fixed bugs such as the AltTester® prefab not being set up correctly when instrumenting the app.

  • Apps can now be instrumented with Unity Cloud Build. See Building from the command line.

  • An option to show or hide the green pop-up at runtime.

  • A Log panel to view the in-game logs at runtime.

Fixes#

  • Fixed WebGL builds in Unity 6.

  • Fixed FindObjectAtCoordinates.

  • Added missing dependencies.

  • Fixed several issues with iOS builds.

Version 2.2.5#

Released 2 April 2025. See the upgrade guide.

  • Fixed a problem with the UPM package.

  • Fixed a problem with the new version panel.

Version 2.2.4#

Released 1 April 2025.

  • Fixed an error caused by conflicting input class definitions when you use custom input. Non-GPL

  • Visual elements generated at runtime can be found. Non-GPL

  • A new SetImplicitTimeout command, which tests can call.

  • The instrumented game notifies you when a new version is available.

  • Fixed a JSON deserialization issue.

  • Fixed an error when the product name contains a colon.

Version 2.2.2#

Released 30 January 2025.

  • A new FindObjectFromObject command finds a child of an object that matches the given conditions.

  • Android and iOS apps instrumented with the Non-GPL package can connect to BrowserStack. Non-GPL

  • Fixed problems related to disconnecting.

Version 2.2.0#

Released 27 November 2024.

  • Updated the GetApplicationScreenSize command.

  • Added an event call for pointerMoveHandler.

  • A new command and changes to support the new UI.