How To Report Bugs
To make bug reporting as quick as possible, we made a bug reporting application for you. When running Unity choose Help->Report a Bug in the menu, or you can access it directly through the executable in the directory where Unity is installed. It will also launch automatically if you experience a crash.
1) Which Type of Issue is it?
A problem with the Editor – Is the Unity Editor not working like you expect it to?
A problem with the player – Are you experiencing trouble with a published game? Please include a note if this problem is only seen on Windows.
Documentation – Have you found an error, or typo, or omission in the docs, in one of the tutorials, or on the website?
Crash bug – Did Unity or a Unity game crash? Should the Unity Bug Reporter application not automatically launch, please launch it at once and use this option.
Services – Are you experiencing performance or integration issues with Unity Ads, Everyplay, Multiplayer, Analytics, Cloud Build or Performance Reporting?
2) Tell us how to reproduce the issue
In order for us to fix the issue, we need to be able to reproduce it. With a precise description of what you did, we can clearly follow your actions and recreate the same situation. The most important thing is telling us exactly how to reproduce the issue.
Knowing how much you have to write can be a little difficult, so here is an example to help you get started:
- Launch Unity while holding the ALT key down
(On Windows, press ALT immediately after clicking the icon)
- Create a new project with no packages imported
- Wait for Unity to launch
- Choose GameObject->Create Empty in the menu
- See that a new GameObject appears in the Scene View
- Choose File->Quit in the menu
- When asked to save, click Don't Save
- See that Unity successfully quits
3) Attach your Project Folder
If the problem is related to anything specific to your Project (like scenes, assets, scripts, or anything else), we need you to upload your Project folder to solve the issue. The best project folders for this kind of testing include only the bare minimum of assets required to reproduce the issue.
To help you reduce the size of your projects and to create minimal reproduction cases, we developed several tools that greatly reduce the required effort.
You can find additional information on how to use these tools here.
With a small, focused project like that, we can isolate and fix the bug very quickly. If you don't have time to narrow down your assets to a bare minimum, you can also send in the full project folder. Small projects are better than large projects, but large projects are better than nothing. Our reporting system supports huge attachments. Please do not upload individual assets because the Project contains relevant data and files that the assets alone do not.
4) Provide your email address
We may need to ask further questions about your issue, so we require a valid email address.
5) What happens next?
When your bug is submitted, you will receive an automatic confirmation email. Each email will include a hyperlink to a web page that contains the current status of the issue. You can check this link at any time. We cannot personally email back every person about every bug report, so please check the status of your issue if you are curious. Generally, all fixes will be rolled out in the next major or minor update to Unity. Keep an eye out for fixes when the new version is released!
News from Unity QA
We’re not just toolsmiths, but wordsmiths too! Read all the Unity QA blogposts past and present.