Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.54f1
6000.1.14f1
6000.2.0b12
6000.3.0a3
6000.4.0a1
6000.5.0a1
6000.6.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
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.