data lost after migrate from 1.0.5.1 to 1.0.5.3

[Edward Liao]

Hello,

I just tested 1.0.5.3 today, and I found a serious issue: after upgrade, some of my previous data configured in 1.0.5.1 is missing from my serialized object.

I was upgrading from 1.0.5.1 to 1.0.5.3, looks like it is not back compatible, is this by design, or just another bug?

Thanks!

Before upgrade.

After upgrade.

[Tor Esa Vestergaard]

Hi, this is a bug, and we apologize for having let it slip through - full backwards compatibility with the serialization is a very high priority for us, and it's very disappointing that this seems to have happened despite our testing. We've heard some indications of this bug with dictionaries, but it's been extremely difficult to reproduce. We will attempt to reproduce it using your example data layout from the pictures - any piece of data helps. Thank you for reporting this issue, and again, we're sorry we let it happen.

Finally, we would appreciate it deeply if you could use your source control to go back, and upload the asset containing the data that is lost on deserialization, for us to inspect when debugging. That would also be a great help!

[Edward Liao]

the data that can not be displayed after migrating to 1.0.5.3.

[Edward Liao]

See attached files, the affected asset has no changes after migrate, but the inspector is not able to display it correctly.

Thanks.

[Tor Esa Vestergaard]

Thank you. We're looking into why this data isn't deserializing properly, and will have a fix ready for you as soon as possible.

[Edward Liao]

Hello,

Any progress on this issue?

For the moment, I need to decide to whether to upgrade 1.0.5.3 or stay 1.0.5.1.

I am worry about continue using 1.0.5.1 will force me to recreate all my data in future.

If you are confident with 1.0.5.3, I will upgrade to it, since the lost I got here is not that harmful. I could manually recreate the data.

[Tor Esa Vestergaard]

Give me a day or two, and this will definitely be fixed. I am dedicating most of today towards this issue, and I will continue tomorrow if it is not fixed today. I wanted to give it a solid go earlier than this, but it's been a crazy weekend and start of the week, so I simply physically haven't had the time. You will have a fix very soon, though.

[Tor Esa Vestergaard]

Alright, using the data in your asset to reconstruct the deserialization process, I was able to work out exactly what was going wrong. I now have a fix for the issue, which I would like you to test to confirm that it works for your data (it definitely should). If you either post your email here, or send me a mail at [e-mail], then I will send you a fixed build for testing.

[Tor Esa Vestergaard]

Issue #217 was marked as a duplicate of this issue.

[Edward Liao]

Awsome!

Please check your mailbox, I just drop you a letter.

[Tor Esa Vestergaard]

Issue is reported resolved.