Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.14f1
2021.2
2022.1
Issue ID
1354586
Regression
No
Message gets logged in the Console when using Debug.LogFormat and the unityLogger.logEnabled is set to false
How to reproduce:
1. Open the attached 'case_1354586.zip' project
2. Open the SampleScene
3. Enter the Play mode
4. Observe the Console
Expected result: The Console is empty
Actual result: 'But you can see this message.' gets logged in the Console
Reproducible with: 2019.4.29f1, 2020.3.15f2, 2021.1.16f1, 2021.2.0b6, 2022.1.0a4
Notes:
- The issue is only reproducible with Debug.LogFormat overload that takes 5 parameters
- The issue is not reproducible with other Debug methods
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a10
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b14
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.24f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.21f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.32f1