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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2020.1):
Fixed in 2020.2.0a4