Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
The upm.log file's debug level includes function calls with confusing names like hxt()
At debug logging level, the upm.log file shows the name of each function that executed in UPM as well as the arguments passed or the value returned. However, the function names appear to be random strings such as "bht()", "fht()" and "xht()".
Steps to reproduce:
1. Go to Edit > Preferences (Windows) or Unity > Preferences (macOS) from the main menu in Unity
2. Set "Package Manager Log Level" to "Debug"
3. Open the upm.log file (https://docs.unity3d.com/Manual/LogFiles.html)
4. In Unity, trigger a Package Manager operation. If the Package Manager window was not open, open it via Window > Package Manager. If the window was already open, trigger a list operation by clicking the Refresh List button in the Package Manager window.
At debug level, the log file should show the names of UPM functions that executed. Since we just executed a List operation, we should see "list()"
We observe lines in the upm.log file such as:
Where "bht", "fht" and "xht" are the function names. Note: The actual function names you observe may differ but they will fit this pattern - they will be 3 random letters followed by parentheses, followed by "args" or "returned" on the next line.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window