Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.30f1
2022.3.10f1
2023.1.14f1
2023.2.0b11
2023.3.0a6
Issue ID
UUM-52881
Regression
No
"Script 'Canvas' has the same name as built-in Unity component. AddComponent and GetComponent will not work with this script." warning when creating a script that has the same name as built-in Unity component
Reproduction steps:
1. Create a new project
2. In the Project window create a new C# Script (Create > C# Script)
3. Name the created script “Canvas”
Expected result: No warnings are thrown
Actual result: “Script 'Canvas' has the same name as built-in Unity component. AddComponent and GetComponent will not work with this script.” warning
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b11, 2023.3.0a6
Reproducible on: Windows 10
Not reproducible on: No other environment tested
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
- Animator Controller throws MissingReferenceException after undoing Layer Creation
- Full stack trace is always printed when an exception occurs in an IL2CPP build
- Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
- Licensing Client fails to launch when opening Unity Hub
- Different custom Shader behavior when GPU Resident Drawer is enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.