ADT known issues
Last updated on November 14, 2024
This table lists the known issues in AccelByte Development Toolkit (ADT). We are currently working to resolve each issue.
| No. | Feature | Issues | Workaround |
|---|---|---|---|
| 1 | Smartbuild | Staging process takes a long time to finish. | Whitelist the Smartbuild cache directory from your system's antivirus or reduce disk utilization for faster staging process. Refer to the Smart Build staging phase takes too long troubleshooting article. |
| 2 | Hub; Playtest Report | 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; a workaround is yet to be determined. |
| 3 | Hub; SDK | Crash video generation is disabled for paths exceeding the 173-character limit. | Switch to the shorter directory. |
| 4 | Hub; SDK | Issue reporter displays blank image for long installation paths (exceeds character limit). | Switch to the shorter directory. |
| 5 | SDK | Linux/server crashes are not sent to ADT in UE5. | Refer to the Additional Steps for Unreal 5.1+ section in Use Unreal Unattended CRC article. |
| 6 | Web; SDK | [Xbox One/Xbox Series X (XSX) Unreal Engine (UE) 4] Hardware information is not sent to ADT. | We are actively investigating a solution; a workaround is yet to be determined. |
| 7 | SDK | The packaged game does not include crash reporting functionality. | Ensure successful build of the Crash Reporter component. If the package process employed RunUAT.bat, ensure the command included the -crashreporter parameter. |
| 8 | Track History | Setting a specific build version from the track history as the head of track will remove the current history associated with that build ID. | We are actively investigating a solution; a workaround is yet to be determined. |
| 9 | Smart Builds | 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. | Relaunch the ADT Hub. |
| 10 | CLI - Smart Builds | Unable to process Smart Builds upload from Linux CLI with error: getaddrinfo() thread failed to start. | Run this command on your Linux terminal: ulimit -n 1000000 and then rerun your BlackBoxCLI command. |
| 11 | Web; CLI | PS4 and PS5 both display incorrect call stacks for crashes sent to ADT Web. | We are actively investigating a solution; a workaround is yet to be determined. |
| 12 | Hub | The auto-deployment process for the PS4 and PS5 does not function properly. | We are actively investigating a solution, but a workaround is yet to be determined. |
| 13 | Web | Inability to integrate with a Jira server. | There's currently no workaround for this issue. The Jira server is temporarily unusable. |
| 14 | Hub | Archived Channels are not displayed in the archived filters on the Discover page archived filters. | There's currently no workaround for this issue. |
| 15 | Hub | Namespace settings cannot be accessed from ADT Hub. | Access namespace settings through ADT Web. |
| 16 | Hub | When ADT Hub fails to download an update, the track will show you the download button, indicating that the download has failed and the data of your previous download is also uninstalled. | Click the download button again, and the ADT Hub will automatically resume the download from where it stopped after being canceled. |
| 17 | Web | Unable to login using Okta SSO for some reasons. | Please contact your namespace Admin to create an account to log in to ADT using email and password. |
| 18 | Hub | Smart Build downloads containing files over 1 GB may experience temporary progress stalls lasting a few minutes. | We are actively investigating a solution. |
| 19 | Hub | The current build doesn't uninstall when updating to a new build while playing the existing one. | Make sure to close the currently played build before updating the track head. |
| 20 | Hub | ADT Hub is installed but it is not generating the shortcut from Windows Start Menu. | Uninstall your current ADT Hub from the computer settings, then delete the entire ADT Hub folder located at C:\Users\%user%\AppData\Local\ab-adt-hub. This deletion will not affect the builds you downloaded from ADT Hub. Reinstalling the ADT Hub will solve the issue. |
| 21 | Hub | Build is marked as empty or no binary when changing the head of the track. | Change the current version to a different one. Revert to the initial version. Select the specific build you want to set as the head of the track. |