Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.54f1
6000.1.14f1
6000.2.0b12
6000.3.0a3
6000.4.0a1
6000.5.0a1
Issue ID
UUM-113009
Regression
No
UI Builder or its Inspector sections corrupt when "Data Source Path" property is replaced with a space
How to reproduce (inconsistent):
1. Create and open a new project
2. Create and open in UI Builder a new UI Document
3. Add some element to the Hierarchy
4. Add any ScriptableObject from ObjectPicket to the “Data Source” attribute
5. Try doing these actions in random order:
- Add a property to “Data Source Path“
- Select the property and replace the string with a Space (then press Enter or save the changes)
- Save (CTRL+S)
- Undo (CTRL+Z) (using this usually helps a lot in reproduction)
- Change ScriptableObjects in “Data Source“
- Deselect and select the element (This usually triggers the corruption)
Expected result: Nothing breaks and nothing corrupts
Actual result: At some moment, the Attributes and Bindings section will fail to expand, and “IndexOutOfRangeException” errors will be thrown in the Console. Or, the UI Builder window will fail to update visual changes done to the UI Builder
Reproducible in: 2023.3.0a2, 6000.0.54f1, 6000.1.14f1, 6000.2.0b12, 6000.3.0a3
Could not test in: 2023.2.0a1 (No Binding section)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- The issue reproduction is inconsistent, but most of the time, when it reproduces, it will just momentarily corrupt the Bindings and Attributes sections of the UI Builder, until the window is reopened
- Only when the sections/UI Builder is corrupted, an “IndexOutOfRangeException“ error will be thrown in the Console
- The issue is easier to reproduce on 6000.2 and 6000.3 versions for some reason
- In version 2023.3.0a2, the editor crashes when the space is pressed after selecting the Data Source Path string
- Sometimes, if saved at the right time/after certain steps, the bug will corrupt the whole file. After reopening the UI Document, no element is visible in the Hierarchy, and no element can be added to the Hierarchy
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment