Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2022.1.X
Votes
0
Found in
2022.1.0a16
Issue ID
1386650
Regression
Yes
UI Builder produces invalid UXML code when overriding an attribute from another UXML document
Reproduction steps:
1. Open the attached project "UxmlBugRepro.zip"
2. Open "SampleScene" Scene
3. Open "UI.uxml" in the Assets Folder
4. In the UI Builder's Hierarchy window expand "root" and "Comp" Components
5. Select the "someLabel" Text component
6. Change the Text value in the UI Builder's Inspector window
7. Save the UI Document
Expected result: UI Document is saved without any issues
Actual result: "System.Xml.XmlException" is thrown, the UI Builder rewrites the UXML code without a forward slash at the end of the AttributeOverrides element statement
Reproducible with: 1.0.0 (2022.1.0a16, 2022.1.0b2)
Not reproducible with: 1.0.0-preview.18 (2019.4.34f1, 2020.3.25f1, 2021.2.6f1, 2022.1.0a15), 1.0.0 (2021.2.7f1)
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 (fix version 2022.2):
Fixed in: 2022.2.0a2
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b5