Search Issue Tracker
By Design
By Design in 2022.1.X
Votes
0
Found in
2020.3.38f1
2021.3.13f1
2022.1.20f1
Issue ID
UUM-16938
Regression
No
MonoImporter logs a warning when a new type has a naming collision with a built-in component
How to reproduce:
1. Open the attached “My project” project
2. Open the “Assets/Animation” script
3. Change the name of the “MyMethod” method to “MyMethod2”
Expected result: No warnings or errors appear in the Console
Actual result: “Script 'Animation' has the same name as built-in Unity component. AddComponent and GetComponent will not work with this script.” warning appears in the Console
Reproducible with: 2020.3.38f1, 2021.3.13f1, 2022.1.20f1, 2022.2.0a12
Not reproducible with: 2022.2.0a13, 2022.2.0b10, 2023.1.0a16
Reproducible on: Windows 10
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
Currently this is by design, as why the is error reported.
Theres currently too much that needs to change to make this work, hopefully we will get there at some point
Resolution Note (2022.1.X):
Currently this is by design, as why the is error reported.
Theres currently too much that needs to change to make this work, hopefully we will get there at some point