Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.16f1
Issue ID
1103759
Regression
No
Serialization layout error thrown in Build when using Generic Classes with fields that only exist in the editor
How to reproduce:
1. Open the user-submitted Project ("Bug - Serialization layout.zip")
2. Build and run the Player with the "development build" option enabled
3. Observe the console error
Expected result: no error is thrown in the build because the #if UNITY_EDITOR directive is used
Actual result: "A script behaviour (probably Test?) has a different serialization layout when loading. (Read 36 bytes but expected 40 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?" error is thrown in the build version
Reproduced in: 2019.1.0a11, 2018.3.0f1, 2018.2.19f1, 2018.1.9f2, 2017.4.17f1
Note: When using a regularClassInstance with the same code the error does not occur
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
We will not add support for this use and it therefore won't be fixed.