Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
0
Found in
5.6.2p4
Issue ID
937501
Regression
No
[UWP] Classes implementing the ISerializationCallbackReceiver interface do not deserialize properly in a StateMachineBehaviour
Steps to reproduce:
1. Open attached project "937501.zip"
2. Build 'main' scene for UWP
3. Open VS solution
4. Build & run on local machine
5. After launch observe VS output
*you can see that the string value is printed out in 'OnAfterDeserialize()'*
*right after 'OnStateEnter()' is called, however, the string value(which was printed out before) is null*
*in this case, integer member value remains the same, while string member value gets nulled*
Expected behavior: 'OnAfterDeserialize()' doesn't erase string member value on finish
Notes:
Not reproducible in Editor
Not reproducible with IL2CPP scripting backend
Reproducible with: 5.6.0b1, 5.6.3f1, 2017.1.0p3, 2017.2.0b5, 2017.3.0a2
Fixed in: 2017.3.0b8, 2018.1.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment