Search Issue Tracker
Fixed
Fixed in 2020.3.41f1, 2021.3.11f1, 2022.1.18f1, 2022.2.0b8, 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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note (fix version 2023.1.0a9):
Fixed in: 2023.1.0a9
Resolution Note (fix version 2022.2.0b8):
Fixed in: 2022.2.0b8
Resolution Note (fix version 2022.1.18f1):
Fixed in: 2022.1.18f1
Resolution Note (fix version 2021.3.11f1):
Fixed in: 2021.3.11f1
Resolution Note (fix version 2020.3.41f1):
Fixed in: 2020.3.41f1