Search Issue Tracker

Fixed in 2020.1

Fixed in 2019.3

Votes

2

Found in

2019.3.0a2

2019.3.0b1

2020.1.0a1

Issue ID

1180719

Regression

No

[SerializeReference] Assets lose its Data when a Class name is changed

Serialization

-

To reproduce:

1. Download attached "SerializeReference.zip" project and open in Unity
2. Select "New Some Thing" gameObject in the Project window
3. Click from the main menu BugReport > Populate Selected Some Thing
4. While "New Some Thing" gameObject is selected in Inspector expand "Element 0" and notice it has a "Left" and "Right" item
5. Open Scripts/SomeThing.cs script
6. Rename the class "RootNode" to "RootNodeNewName" and save it
7. Switch back to Unity Editor

Expected results: Renaming class names should not cause Fata loss
Actual results: Observe that the Data is gone. "Element 0" no longer shows a "Left" and "Right" item and Console outputs Error:

"Unknown managed type referenced: [Assembly-CSharp] .RootNode"

Notes:
- This issue appears on both Windows and macOS
- Could not check on Unity 2019.3.0a1 because the project becomes corrupted
- Customer copied the example snippet for the new [SerializeReference] feature from https://forum.unity.com/threads/serializereference-attribute.678868/#post-4543723
- Another Forum link: https://forum.unity.com/threads/serializereference-data-loss-when-class-name-is-changed.736874/#post-4915595

Reproduced on Unity 2019.3.0a2, 2019.3.0b3 and 2020.1.0a1

Comments (4)

  1. 00b6017718af140fd7b2db01782614b3?d=mm

    webbertakken

    May 25, 2020 18:24

    Happens on 2019.3.8f1 too

  2. 369fbf635dee4d78e9b11e09265442c4?d=mm

    KMacro

    Feb 26, 2020 00:33

    I am still seeing this issue in 2019.3.2f1 and 2020.1.0a24.

    This behavior also occurs when the class is removed entirely from the assembly.

    A huge consequence of this is that any collection containing an object that references the changed/deleted class will have all of its entries nullified, regardless of if they themselves have a reference to the class.

    I have reported my specific problems in ticket #1218905.

  3. F14cae41ffb3690c47d76af33dec2e42?d=mm

    kvfreedom

    Dec 05, 2019 08:05

    Should be fixed in 2019.4

  4. 77c93f8de558bd9b1ca4442fc3db0991?d=mm

    kyuskoj

    Nov 27, 2019 19:33

    fixed in 2020 only? what about 2019.3

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.