Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.36f1
Issue ID
UUM-68500
Regression
No
Warning "Script 'name' has the same name as built-in Unity component" is shown in the Console window when the script is not a MonoBehaviour
Reproduction steps:
1. Open the “Bug Reports.zip” Project
2. In the Project window, go to Assets > MyLibrary
3. Right-click the “Collider.cs” script, and select Reimport
4. Observe the Console window
Expected result: No errors or warnings are thrown
Actual result: “Script 'Collider' has the same name as built-in Unity component” warning is thrown
Reproducible with: 2021.3.36f1 2022.2.0a1
Not reproducible with: 2022.3.22f1, 2023.2.16f1, 6000.0.b13
Fixed in: 2022.2.0a2
Reproducible on: Windows 10 (by reporter), Windows 11
Not reproducible on: No other environment tested
Notes:
- This warning should only be thrown when the script has a MonoBehaviour class
- For some reason, the warning only appears for a split second and then disappears for me, but looks like it stays for the user
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
- [HDRP] HDAdditionalLightData.RequestSubShadowMapRendering on directional lights breaks cascade shadows rendering
- Memory leaks when Instantiating Objects with SerializeReference
- Currently selected Action Map switches to the first Action Map in the list and it's first Action when editing the Binding Path of a newly created Action
- "F" default focusing Unity shortcut zooms out when the first time focusing the GameObject
- DropdownField options added with PointerDownEvent are not shown when clicking the DropddownField for the first time
Resolution Note:
Affected version no longer supported.