Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2019.1.10f1
2019.2.0b9
2019.3.0a6
Issue ID
1169801
Regression
Yes
SerializedProperty.objectReferenceInstanceIDValue asserts if Update() has been called for the serialized object
How to reproduce:
1. Open the attached "SerializationBug.zip" project
2. Open scene "Sample Scene"
3. Select "Bug" in the Hierarchy
4. Right-click the "Reproduce Bug" component and select "Execute Bug"
Expected results: There are no errors in the Console
Actual results: There are multiple assertion failures in the Console
Reproducible with: 2019.1.11f1, 2019.2.0b10, 2019.3.0a10
Not reproducible with: 2017.4.30f1, 2018.4.4f1, 2019.1.9f1, 2019.2.0b8, 2019.3.0a5
Notes: Commenting line 21 in the ReproduceBug.cs (which causes the serialized object not to be updated anymore) stops the issue from reproducing
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.0a12