Search Issue Tracker
Fixed in 2020.3.41f1
Fixed in 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a9
Votes
0
Found in
2020.3.36f1
2021.3.6f1
2022.1.9f1
2022.2.0b1
2023.1.0a3
Issue ID
UUM-9221
Regression
No
The wrong Component/Class gets added when adding a Nested Class via Script that has a duplicate Class elsewhere
How to reproduce:
1. Open the user-attached “YouHaveToBeKiddingMeBro.zip” project
2. Enter Play Mode
Expected result: “Added the correct type” is printed
Actual result: “Added the wrong type” is printed
Reproducible with: 2020.3.36f1, 2021.3.6f1, 2022.1.9f1, 2022.2.0b1, 2023.1.0a3
Reproduced on: macOS Monterey 12.0.1
Note:
- If “Enter Play Mode Options” is turned off the issue is not reproducible (Edit → Project Settings → Editor)
- If “Reload Domain” is turned on the issue is not reproducible (Edit → Project Settings → Editor)
- If the issue is not reproducing, re-opening the project forces the issue to reproduce once again
- Reimporting or making any change to the script fixes the issue unless you re-open the project
- Reproducible on a new project
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note (fix version 2023.1):
Fixed in: 2023.1.0a9
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0b8
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.18f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.11f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.41f1