Console Window
Unity Test Runner

Log Files (Archivos de Registro)

There might be times during development when you need to get information from the logs of the standalone player you’ve built, the target device, the Package Manager or the Editor. The log files are useful when you have experienced a problem, to find out exactly where the problem occurred.

On macOS, you can access the Player, Package Manager, and Editor logs through the standard Console.app utility.

On Windows, the Package Manager and Editor logs are placed in folders which are not shown in the Windows Explorer by default. See below for more information on where to find the logs.

Package Manager

To view the Package Manager log, navigate to the Unity log folder:

OS #Log Files (Archivos de Registro)
macOS ~/Library/Logs/Unity/upm.log
__Windows __ C:\Users\username\AppData\Local\Unity\Editor\upm.log

On macOS, you can also use the standard Console.app utility to find the log under the ~/Library/Logs/Unity folder.

On Windows, you can find the Editor log file in the local application data folder <LOCALAPPDATA>\Unity\Editor\Editor.log, where <LOCALAPPDATA> is defined by CSIDL_LOCAL_APPDATA.

Editor

To view the Editor log, select Open Editor Log in Unity’s Console window.

OS #Log Files (Archivos de Registro)
macOS ~/Library/Logs/Unity/Editor.log
__Windows __ C:\Users\username\AppData\Local\Unity\Editor\Editor.log

On macOS, you can also use the standard Console.app utility to find the log under the ~/Library/Logs/Unity folder.

On Windows, you can find the Editor log file in the local application data folder <LOCALAPPDATA>\Unity\Editor\Editor.log, where <LOCALAPPDATA> is defined by CSIDL_LOCAL_APPDATA.

Player (Reproductor)

OS #Log Files (Archivos de Registro)
macOS ~/Library/Logs/Unity/Player.log
__Windows __ C:\Users\username\AppData\LocalLow\CompanyName\ProductName\Player.log
Linux ~/.config/unity3d/CompanyName/ProductName/Player.log

On Windows and Linux standalones, you can change the location of the log file, or stop Unity from logging to it. For more information, see the Command line arguments documentation.

iOS

El registro del dispositivo puede ser accedido en Xcode vía la consola GDB o la Organizer Console. El último es útil para obtener registros crash cuando su aplicación no estaba corriendo a través del depurador de Xcode.

See the documentation on Troubleshooting and Reporting crash bugs for information about debugging crashes and issues.

Android

Use the logcat console to access your device log. To use it, launch the adb application in the Android SDK/platform-tools directory with the logcat parameter:

$ adb logcat

You can also use the Dalvik Debug Monitor Server (DDMS) to access the logcat console. To launch DDMS, start it either from Eclipse or from inside the Android SDK/tools. DDMS also provides a number of other debug-related tools.

Universal Windows Platform

Dispositivo #Log Files (Archivos de Registro)
Escritorio %USERPROFILE%\AppData\Local\Packages<productname>\TempState\UnityPlayer.log
Windows Phone You can retrieve your Windows Phone log with Windows Phone Power Tools. The Windows Phone IsoStoreSpy also provides a number of helpful debugging tools.

WebGL

For WebGL, Unity writes the log output to your browser’s JavaScript console.

Accediendo Log Files (Archivos de Registro) en Windows

On Windows Vista and Windows 7, make the AppData folder visible in Windows Explorer using Tools > Folder Options > View (tab). The Tools menu is hidden by default. Press the Alt key once to display it.

On Windows 10, make the AppData folder visible in Windows Explorer using View > Show/hide and enabling the Hidden items option.


Console Window
Unity Test Runner