Search Issue Tracker
Fixed in 2020.1.X
Votes
1
Found in
2018.3.0a6
2018.4.1f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1164099
Regression
No
SerializableObject.GetIterator() throws ArgumentNullException when UnpackPrefabInstance() is called on an instantiated Prefab
How to reproduce:
1. Open the "SampleScene" Scene in the attached "case_1164099.zip" Unity project
2. In the Hierarchy tab, select the "TestUnpackPrefabInstance" GameObject
3. In the Inspector tab, click "Create and Unpack Prefab Instance"
4. Observe the Console tab
Expected result: the "ExamplePrefab" Prefab gets instantiated and unpacked without any errors thrown
Actual result: an "ArgumentNullException: Value cannot be null. Parameter name: _unity_self" error is thrown
Reproducible with: 2018.4.3f1, 2019.1.9f1, 2019.2.0b8, 2019.3.0a8
Note: unable to test on 2017.4 and 2018.3.0a1 through 2018.3.0a5 since UnpackPrefabInstance has not been introduced in these versions.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.1):
Fixed in 2020.2.0a4