Search Issue Tracker
Fixed
Fixed in 6000.0.12f1, 7000.0.0a2
Votes
0
Found in
6000.0.5f1
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
- TableEntryAdded event is not triggered when a new entry is added in the Localization Tables window
- The macOS Player is built to a different folder than the selected one when the Player is built on Windows
- Editor memory leak in VisualElement when recompiling in a blank URP project
- Project Auditor suggests to update package to a lower version than installed when the recommended package version is not the latest version
- Low performance when multiple meshes using BlendShape are rendered on screen
Add comment