Search Issue Tracker
Fixed
Fixed in 6000.0.12f1, 7000.0.0a2
Votes
0
Found in
6000.0.5f1
7000.0.0a1
Issue ID
UUM-73716
Regression
No
An error is thrown when a custom class UXLElement Component is derived from a normal component
Reproduction steps:
1. Create a new project
2. Import the “CustomToggle.cs“ Script to the Project’s Assets folder
3. Observe the Console
Expected result: No errors are present
Actual result: “A UxmlElement for the type CustomToggle in the assembly Assembly-CSharp was already registered from another assembly Assembly-CSharp.“ Error is logged
Reproducible with: 6000.0.5f1,
Couldn’t test with: 2021.3.39f1, 2022.3.32f1 (due Script errors, missing features)
Reproducible on: M1 MacOS 14.4.1
Not reproducible on: No other environment tested
Note: This error does not prevent playing in editor or building the project or otherwise interfere with expected functionality, it just clutters the console window after each recompile until it is cleared
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ListView fails to display items when the source list is cleared and a single element is added
- UI Toolkit ':hover' state remains active when another panel is drawn over the hovered element and Touch input is used
- Unsupported Orient modes can be selected and throw errors when using Strip VFX
- "Tab" key exits the name text field in the VFX Graph tab when renaming the Property
- Shader warnings are thrown when deleting blocks in the Ribbon VFX Graph
Add comment