Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.47f1
2022.3.56f1
6000.0.35f1
6000.1.0b3
6000.2.0a1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-93284
Regression
No
A script cannot be attached to a GameObject when there is another script that is generic with the same name in a different folder
Steps to reproduce:
1. Open the attached “ClassNameBug.zip” project
2. Open the “SampleScene”
3. In the “Assets/0param” folder find “MyScript.cs”
4. Attach the script to a GameObject within the Project Hierarchy
5. Observe the results
Expected result: The “MyScript.cs” file is added as a Component
Actual result: An error message is shown
Reproducible in: 2021.3.47f1, 2022.3.56f1, 6000.0.35f1, 6000.1.0b3
Reproducible on: Windows 11, 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
- Video does not play in macOS build when built app is placed in a path with a space in it on a specific project
- Crash on AuxWindowManager::OnGotFocus when trying to maximize a tab while Visual Effect Graph window is open
- “NullReferenceException: Object reference not set to an instance of an object” error is thrown when
- [Metal] Game freezes after command buffer Timeout error
- Addressables Report window UI is broken when opening via Build > New Build > Default Build Script
Resolution Note:
The case is very specific with several unlikely circumstances and there is a lot of ways to avoid it. Here are a few:
* Put scripts in different assemblies (Just creating AssemblyDefinition file next to one of the scripts works)
* Put scripts in different namespaces
* Use different class names (if a generic class is inheriting a MonoBehaviour you might use suffix "Base" as it is likely to get inherited by class that you'll actually use on GameObject)