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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
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