Search Issue Tracker
Fixed in 2021.3.34f1
Fixed in 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X, 7000.0.0a1, future release
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.18f1
2023.2.0b14
2023.3.0a10
Issue ID
UUM-16958
Regression
Yes
The asset doesn't get pinged in the Project window when clicking on error in the Console
How to reproduce:
1. Open the attached project “IN_17578”
2. Click on the error “error CS0103” or “error CS0201“ in the Console
3. Observe the Project window
Expected result: asset with error gets pinged
Actual result: asset with error doesn’t get pinged
Reproducible with: 2021.1.0a6, 2021.3.9f1, 2022.1.19f1, 2022.2.0b9, 2023.1.0a12
Not reproducible with: 2020.3.40f1, 2021.1.0a5
Reproducible on: Windows 10 Pro
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UVCS] Wrong folder moved to changelist after shelve/unshelve sequence
- Object Selector becomes unresponsive when selecting root UI Document as Data Source for Add Binding in UI Builder
- Search #Light.m_Shadows.m_Type query block does not detect default Light objects in Scene unless they were modified
- Shader Graph "Create Node" menu has a doubled text in search when the text was deleted replaced to the space and then the exact same text was entered
- Multiple non interactable Worker Processes are active when calling undelayed editor processes in the InitializeOnLoadMethod
Add comment