Problem diagnosis and reporting in Unity development

During the development of Unity-based plugins or applications, runtime exceptions or logical errors are inevitable. To assist developers in quickly locating and resolving issues, the Unity Plugin provides a series of built-in diagnostic and debugging tools. This chapter introduces these commonly used debugging methods and auxiliary functions, covering the complete process from real-time log viewing, enabling developer mode, to problem data collection and reporting.

• UI messages

  Explains how the runtime system displays errors, warnings, and other diagnostic information at the UI level, and clarifies the classification criteria and meanings of these messages for rapid problem type identification.

• Developer mode

  Describes how to activate developer mode during application runtime and the advanced debugging features available in this mode: visual debugging layer, EIF/EED file recording.

• Recording EED dump files

  Details how to trigger and record EED files, which contain contextual information such as key events, sensor data, and system status; also explains how to export these dump files from the device and use them for offline analysis.

• Problem reporting

  Guides users on how to properly submit problem feedback, including required attachments like logs, dump files, reproduction steps, etc., to improve issue resolution efficiency.

Related functional components include:

• DiagnosticsController component

  This component is the core controller of the diagnostic system, responsible for coordinating functions such as log recording, status monitoring, and dump generation.