Unity WebGL content cannot currently be debugged with MonoDevelop or Visual Studio, which can make it difficult to find out what exactly is going wrong with your content. Here are some tips on how to get information out of your build.
Unity WebGL does not have access to your file system, so it will not write a log file like other platforms. However, it will write all logging information which would normally go to the log file (such as Debug.Log
, Console.WriteLine
or Unity’s internal logging) to the browser’s JavaScript console.
For debugging purposes, you may typically want to make a development build in Unity (the Development Build checkbox in the Build Settings window). Development builds allow you to connect the profiler, and they will not be minified, so the emitted JavaScript code will still contain human-readable (though C++-mangled) function names. These can be used by the browser to display stack traces when you run into a browser error, or when you throw an exception and exception support is disabled, or when using Debug.LogError
. Unlike the managed stack traces which you can get when enabling Full exception support (see below), these stack traces will have mangled names, and contain not only managed code, but also the internal UnityEngine code.
WebGL has different levels of exception support (See the page on Building for WebGL). By default, Unity WebGL will only support explicitly thrown exceptions. You can enable Full exception support which will then emit additional checks in the IL2CPP generated code to catch access to null references and out-of-bounds array elements in your managed code. These additional checks will significantly impact performance and increase code size and load times, so this mode is only recommended for debugging.
Full exception support will also emit function names to generate stack traces for your managed code. So you will see stack traces in the console for uncaught exceptions and for Debug.Log
statements, and you can get a stack trace string using System.Environment.Stacktrace
.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Is something described here not working as you expect it to? It might be a Known Issue. Please check with the Issue Tracker at issuetracker.unity3d.com.
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thanks for helping to make the Unity documentation better!