ADT known issues
Below is a list of known or common issues in ADT. We are actively working to resolve each of them.
[Smart Build] Track stays under "In queue" status even no other Smart Build activity is running
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
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\MyGameinstead ofC:\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)
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\MyGameinstead ofC:\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
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
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 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
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.