Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0f2
Issue ID
1066154
Regression
No
Editor Only Serialized Fields are being accessed from a DLL during playtime in a built Player
To reproduce:
1. Open the user's attached project
2. Build a Windows player with the Development Build option selected
3. Run the build
Expected result: The Only in Editor Serialized Field \is not accessed in the built Player
Actual result: The Only in Editor Serialized Field is being accessed in the DLL but not in the script
Reproduced with: 2017.4.9f1, 2018.1.9f1, 2018.2.5f1
Not reproduced with 2018.3 because of a Dev Console bug. It has been reported already.
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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.