Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0b8
Issue ID
1050196
Regression
No
[IL2CPP] Build fails due to incorrect script's serialization
Steps to reproduce:
1. Download 1050196_repro.zip
2. In the Player setting switch to IL2CPP backend
3. Build "SampleScene" scene
Expected results: Build successfully completes.
Actual results: Serialization error appear in the Console and build fails.
Error:
Type '[Assembly-CSharp]test' has an extra field 'FloatVariable' of type 'System.Single' in the player and thus can't be serialized
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
Reproduced with: 2018.3.0a2, 2018.2.0b9, 2018.1.5f1, 2017.4.6f1, 2017.1.4f1
Not reproducible on Mono and .NET (UWP platform) backends
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
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.