Search Issue Tracker
Fixed
Fixed in 2022.3.56f1, 6000.0.35f1, 6000.1.0b2, 7000.0.0a17
Votes
0
Found in
2022.3.55f1
6000.0.30f1
6000.1.0a9
Issue ID
UUM-91487
Regression
Yes
Build failure errors are cleared in console before you can read them
*Steps to reproduce:*
# Create an empty URP project.
# Import attached SpritePostProcessor.cs script to the project folder.
# With the console visible, Build & Run.
*Actual results:* Domain reloads, window repaint occurs and the console errors are cleared before you can click on them to see more information.
*Expected results:* Console errors from failed build should remain visible.
*Reproducible with versions:* 6000.1.0a9, 6000.0.30f1, 2022.3.55f1, 2022.3.52f1
*Not reproducible with versions:* 2022.3.51f1, 2021.3.45f1
*Tested on (OS):* Windows 10, Windows 11
*Notes:*
* To report on an issue about a build error, I had to very quickly take a screenshot. There seems to be no way to click on errors for more details.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Particle System emission ignores the Sprite Atlas when using a Material that has the "Include in Build" setting unchecked
- [Android] [Windows] The frame buffer is replaced incorrectly when using Framebuffer Fetch
- Crash on Scripting::SetCachedPtrOnScriptingWrapper(ScriptingObjectPtr, Object*) when exiting a project
- WASM Heap size greatly increases when UI elements are present in a WebGL build
- Crash on mdb_node_add when opening a specific project with a corrupted Library
Add comment