ADT Unity エラーレポーティング (Alpha)

Last updated on March 11, 2026

Overview

The ADT Unity Engine Crash Reporter helps developers identify and resolve crashes in their Unity game builds. Similar to ADT Unreal Engine crash reporting tool, this feature collects crash data—such as call stacks, logs, and module information—and presents it via the ADT Web, streamlining the debugging process.

Supported Crash Types in Unity

Crashes in Unity generally fall into two categories: Native and Managed. ADT supports both types for both Windows and Android platforms.

Crash Type	Description
Native	Crashes originating from the engine or native plugins.
Managed	Crashes originating from the C# code in Unity scripts.

1. Native Crashes

   Native crashes occur in low-level parts of the engine or external native libraries. They are typically:

   • Triggered by memory corruption, hardware issues, or bugs in the Unity engine or native plugins.
   • Difficult to diagnose, as they often provide limited visibility into the game's managed code.
   • Symbol files required for detailed stack traces.
     Example: A buffer overrun in a native plugin causes Unity to crash before managed scripts execute.

2. Managed Crashes

   Managed crashes occur in the C# code written by developers. These are:

   • Easier to diagnose, as the stack trace usually points to specific scripts or functions.
   • Useful for identifying logic errors, null reference exceptions, or other runtime issues in managed code.
     Example: A NullReferenceException in an Update loop during gameplay on an Android device.