Search Issue Tracker
Fixed
Fixed in 6000.5.X, 6000.5.0a4
Votes
0
Found in
6000.4.0a5
6000.5.0a2
Issue ID
UUM-128318
Regression
No
UI Builder Window breaks and the Editor has to be restarted when using Global Built-in Default Runtime Theme
Steps to reproduce:
- Open any Project
- Navigate to UI Toolkit Project Settings and set "Editor (for Editor Extension Authoring)" to "Built-in Default Runtime Theme"
- Create a UI Document Asset and open it in UI Builder
- Select the root of the UI Document in the Hierarchy and enable "Editor Extension Authoring" checkbox flag
- Observe the Console
- In the UI Builder Window try opening the dropdown menu for the Runtime Theme
- Close the UI Builder Window and open the Asset or any other UI Document Asset
Actual results: Error "NullReferenceException: Object reference not set to an instance of an object
UnityEditor.UIElements.ThemeUtility.NicifyThemeName" is logged in the Console, in some cases Users cannot open the Dropdown Menu for the Theme, UI Builder Window breaks, Editor has to be restarted
Expected results: Users are able to use the Built-in Theme
Reproducible with versions: 6000.4.0a5, 6000.5.0a2
Not reproducible with versions: 6000.0.63f1, 6000.2.14f1, 6000.3.0f1 (No Global Themes)
Tested on (OS): Windows 11, macOS Tahoe 26
Notes: UI Builder also breaks if the theme is set in UI Builder
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
Add comment