Search Issue Tracker
By Design
Unknown (hidden) 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
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