Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.52f1
6000.1.10f1
6000.2.0b2
6000.2.0b8
6000.3.9f1
6000.4.0b9
6000.5.0a7
6000.6.0a1
Issue ID
UUM-110417
Regression
No
UI Builder window corrupts when a custom binding throws an exception
How to reproduce:
1. Open the “IssueUIBuilder.zip” project. Ensure that the localization package version is 1.5.4.
2. Open the “UIDocument.uxml” file
3. Maximize, then un-maximize the UI Builder window
4. Observe the UIBuilder window
Expected result: The panel and UI Builder window are fully functional
Actual result: The whole panel is black
Reproducible in: 6000.0.52f1, 6000.1.10f1, 6000.2.0b2, 6000.2.0b8
Not reproducible in: 6000.3.0a1
Fixed in: 6000.3.0a1
Could not test in: 2022.1.0a1, 2022.3.64f1, 2023.2.0a23 (Not able to bind localization strings)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Reproduces when the string is bound to other UI Builder fields, too
- After reproduction, other tabs can be opened by clicking where the tab headers should be. Then, selecting the UI Builder tab will freeze that panel again
- If the UI Builder is opened through the UXML file, the UI Builder will render correctly
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.