Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3.0b9
2020.2
Issue ID
1258112
Regression
Yes
UI Toolkit debugger throws exceptions when inspector Package manager window
UI Toolkit debugger throws exceptions when inspector Package manager window
Reported by Ethan Li
Steps to reproduce:
1) Open any Unity project
2) Open Package Manager window
3) Inspect any element under the root visual element
Expected: no exception is thrown and selectors are displayed
Result: exception occurs
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.UIElements.Debugger.MatchedRulesExtractor.<FindStyleSheets>g__RecursivePrintStyleSheetNames|4_0 (UnityEngine.UIElements.StyleSheet importedSheet, UnityEditor.UIElements.Debugger.MatchedRulesExtractor+<>c__DisplayClass4_0& , UnityEditor.UIElements.Debugger.MatchedRulesExtractor+<>c__DisplayClass4_1& ) (at /Users/antoine/Documents/unity-imgui/External/MirroredPackageSources/com.unity.ui/Editor/Debugger/StylesDebugger.cs:399)
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a19