Skip to main content

Crash Reporter Issues

Last updated on

Overview​

Once you have built and uploaded your game, you may notice some errors in the operation of AccelByte Development Toolkit. A couple of common causes are described in this topic.

The steps in this section will explain how to troubleshoot problems with the Crash Reporter.

Watch this snippet for how to add videos and hardware information to your game crashes

The crash video is missing​

If your game crashes, the information about the crash is uploaded to the ADT service. When you use the service to check the information, you may find that your crash video is missing.

Here is a way to make sure that doesn't happen again:

  1. Check your configuration. Make sure you actually enabled this feature, see the video above.
  2. Make sure you have integrated the ADT Unreal SDK properly.
  3. Wait for a few seconds before you click the Send and Close button on the Crash Reporter window since it takes a few seconds to write the video file.

Crash Reporter shows on the wrong section​

This is another common error caused by incorrect setup.

If you have built your game on a shipping build but, after making the game crash, the crash report is showing on an editor build instead, you need to make sure you have uploaded the PDB file using our CLI.

Last updated on