Skip to main content
Version: 14 May 2024


This section reviews different steps you can take to troubleshoot problems you may encounter when using Application Simulator. Topics covered include:

Looking at the Event Log and Log Files

The Application Simulator separates logging information into an Event Log and log files are saved to your local drive. When you launch the Application Simulator from Unity, the Unity log output goes to the Unity console, not the ML Hub logs.

You can view each of the logs by using the Application Simulator menu options.

Show Logs Button in the Application Simulator Menu

You can bundle all of the logs and runtime/error information by using the Save Diagnostic Logs… button. This is useful for reporting errors encountered when using the Application Simulator. It will generate a .zip file that you can unpack to inspect before sending to Magic Leap Developer Support.

You can control the verboseness of the log files by setting the log level to filter out messages that do not meet a minimum level of priority. The default log level is Info, which filters out all messages below the priority level of Info. Do not use the log level Debug unless trying to reproduce or report a bug, as that slows the Application Simulator considerably.

To set the log level:

  1. Expand the Application Simulator Activities menu, and then click Settings.
  2. Select the Log Level.

You may use the following as a template for your message. Remember to attach the .zip of your log files as well:

  • OS and Version:
  • Graphics card or chipset:
  • Details:
    • What were you doing when the problem occurred?
    • Which mode were you using: Simulator or Device?
    • What 3D engine or development platform were you using?
    • Add any additional details pertinent to the problem.

Data Your Report File Contains

These log files include diagnostic information from the user interface, the Application Simulator server, and the Application Simulator app, and could potentially contain information that is either proprietary to you or that might identify you in some way. Examples of such information include and are not limited to:

  • Your user name
  • Path names on your local hard drive
  • Any log messages from the ml_logging APIs
  • List of installed packages and versions
  • ML Hub frontend layout
  • Java crash reports
  • adb logs from default connected device
  • Eclipse/ML Hub logs
  • Application Simulator backend logs
  • Unity editor logs

Protecting Your Privacy

Before sending or attaching the .zip file of the logs to report an error, open the .zip file and view the contents of the logs to make sure you are not sending any information you don't want public.