Search Issue Tracker
Fixed in 2020.3.39f1
Fixed in 2020.3.X, 2021.3.X
Votes
0
Found in
2020.3.37f1
2021.3.6f1
Issue ID
UUM-10043
Regression
No
[Backport] GameObject reference is null when creating it inside Reset() function and assigning Script as component
GameObject reference is null when creating it inside Reset() function and assigning Script as a component when there is Timeline window opened in the Editor
How to reproduce:
1. Open user's project "ResetTest.zip"
2. Open "SampleScene" Scene
3. Click on "GameObject" in the Hierarchy window
4. In the Inspector window, right-click on "New Behaviour Script" and choose Reset
5. Observe console
6. Remove the "New Behaviour Script" component from the "GameObject"
7. Add "New Behaviour Script" Script from "Scripts" folder to "GameObject"
8. Observe console
Expected results: Same Console message (Generated GameObject (UnityEngine.GameObject)) after 4th and 7th step
Actual results: Console logs out null
Reproducible with: 2019.4.27f1, 2020.1.17f1, 2020.2.7f1, 2020.3.9f1, 2021.1.0a8, 2021.1.8f1, 2021.2.0a17
Couldn't test with: 2018.4 (Failed to downgrade to a functioning project)
Note: Closing Timeline window results in same Console message both after 4th and 7th step
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.39f1