Search Issue Tracker
Duplicate
Votes
19
Found in
2019.2.0b7
2019.2.2f1
2019.3.0a7
2020.1.0a1
Issue ID
1183965
Regression
No
"Identifier uniqueness violation" warning pops up when adding multiple MonoBehaviour to model prefab root via AssetPostprocesso
How to reproduce:
1. Open attached Unity project
2. Reload "MyCustomModel" asset
Result: Warning appears:
Identifier uniqueness violation: 'Name://RootNode, Type:MonoBehaviour'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Reproduced with: 2019.2.7f1, 2019.3.0b5, 2020.1.0a5.
Not reproduce with: 2017.4.32f1, 2018.4.10f1.
(Note: It was not reproducible before because the warning just didn't exist. The bug was always there)
How to see expected behavior:
1. Open CustomModelImport.cs script
2. Remove 11 or 12 line
3. Reimport model
Result: There is no warning in a Console window
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
It's a problem in our design, we only take C++ type, so all MonoBehaviours to us is of same type. We would like to fix it, but there is no real way of fixing it without breaking backwards compatibility for all projects. We're tracking it in our internal system.