ADT known issues

Last updated on August 10, 2026

Below is a list of known or common issues in ADT. This list is actively maintained and updated as each issue is resolved.

[Smart Build] Track stays under "In queue" status even no other Smart Build activity is running​

ADT Distribution label — Smart Build queue statusADT Hub label — Smart Build queue status

Under certain error conditions, the Smart Builds CLI may fail to terminate properly. This may cause users to encounter an "In queue" blocker when downloading another smart build.

Workaround: Relaunch the ADT Hub to turn the CLI off and back on again.

Crash video generation fails for paths exceeding 173-character limit​

ADT Health label — crash video generationADT SDK label — crash video generation

Microsoft Windows has a well-known file path length limitation of 260 characters (MAX_PATH). In some cases, specific operations may start failing when file paths exceed approximately 173 characters. When the ADT SDK is installed inside the Plugins folder of an Unreal game project, the full file path can become excessively long—especially if:

  • The game project has a deep directory structure, or

  • The project folder or parent folders use long directory names.

This can cause the ADT application to fail to access required files, which may lead to issues such as crash video generation failures or other unexpected behaviors.

Workaround: To avoid hitting this limitation:

  • Place your game project in a shallow directory (e.g., C:\Projects\MyGame instead of C:\Users\Username\Documents\Unity\LongFolderName\AnotherLongFolderName\MyGame).

  • Use shorter folder and file names where possible.

Avoid nesting the project under too many levels of subdirectories.

Issue Reporter shows blank image for long installation paths (character limit exceeded)​

ADT Health label — Issue Reporter blank imageADT SDK label — Issue Reporter blank image

Microsoft Windows has a well-known file path length limitation of 260 characters (MAX_PATH). In some cases, specific operations may start failing when file paths exceed approximately 173 characters. When the ADT SDK is installed inside the Plugins folder of an Unreal game project, the full file path can become excessively long—especially if:

  • The game project has a deep directory structure, or

  • The project folder or parent folders use long directory names.

This can cause the ADT application to fail to access required files, which may lead to issues such as crash video generation failures or other unexpected behaviors.

Workaround: To avoid hitting this limitation:

  • Place your game project in a shallow directory (e.g., C:\Projects\MyGame instead of C:\Users\Username\Documents\Unity\LongFolderName\AnotherLongFolderName\MyGame).

  • Use shorter folder and file names where possible.

Avoid nesting the project under too many levels of subdirectories.

[Xbox One/XSX] Hardware info not sent to ADT​

ADT Health label — Xbox hardware infoADT SDK label — Xbox hardware info

Hardware information from Xbox One and Xbox Series X is not sent to ADT. This is likely due to platform restrictions that prevent Xbox devices from sharing system-level hardware data with third-party applications.

Workaround: If hardware information is required for troubleshooting or reporting, developers may need to retrieve this data manually or use Xbox-approved APIs that comply with Microsoft's privacy policies.

Crashes during playtest completion are missing from reports when crash files are still processing​

ADT Playtest label — playtest crash reportingADT Hub label — playtest crash reporting

Crashes that occur upon playtest completion do not reflect in reports when the corresponding crash files are undergoing processing by the Back-End (BE).

*We are actively investigating a solution, but a workaround is yet to be determined.

Inability to integrate with Jira server​

ADT Web label — Jira integration

ADT Web and Jira server integration is currently disabled. When attempting to establish a connection, a “This Jira page can’t be found” error is displayed, preventing a successful integration.

Workaround: There’s currently no workaround for this issue. The Jira server is temporarily unusable at the moment.

Failed Hub update removes previous data and shows download button​

ADT Hub label — failed Hub update

When ADT Hub fails to download an update, the track will show the download button, indicating that the download has failed and the data of your previous download is also uninstalled.

Workaround: Click the download button again, and the ADT Hub will automatically resume the download from where it stopped after being canceled.

[macOS] AI Assistant cannot guide automatic MCP server connection​

ADT Hub label — macOS AI Assistant

On macOS, the ADT Hub AI Assistant cannot yet guide users through automatic MCP server connection.

Workaround: Connect the MCP server manually. Support for guided automatic connection on macOS is planned for a future release.

Promote Build to Steam: "Set Live on Default Branch" not yet available​

ADT Distribution label — Promote Build to SteamADT Hub label — Promote Build to Steam

In this Alpha release of Promote Build to Steam, "Set Live on Default Branch" is not available from ADT Hub.

Workaround: Approve and set the build live manually using the Steam Mobile App. Support for setting a build live on the default branch directly from ADT Hub is planned for a future release.

Last updated on
On this page