Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.1.0f2
Issue ID
1036092
Regression
No
Error is thrown after fixing the multiple same serialized fields issue in class inheritance hierarchy
How to reproduce:
1. Open attached project "New Unity Project (1).zip" and scene "Sample"
2. In Hierarchy window, select "Main Camera" (in Console window, "The name is serialized multiple times" error appears)
3. In Project window, open "ParentClass" script and comment out "[SerializeField] private int _value" line
4. Go back into Unity editor and observe Console window
Expected result: no errors appear
Actual result: in Console window, a misleading "The same field name is serialized multiple times in the class or its parent class" error appears
Reproducible with: 2017.1.3p4, 2017.2.3f1, 2017.4.3f1, 2018.1.1f1, 2018.2.0b
Note: the error is thrown only once after coming back to the Editor
-
nostklay
Mar 08, 2023 19:42
I have same issue and only way is changing the variable names altough they are private members. this is so silly.
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
- Audio Mixer does not change volume when lowering volume on an Audio Mixer loaded from AssetBundles
- Error “Value cannot be null. Parameter name: key UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” thrown and Addressables build fails when "Include in Build" is disabled and using Addressables For Android package
- “error CS0433: The type 'CodeBinaryOperatorType' exists in both 'System.CodeDom and 'System" compilation errors are thrown when opening a specific project
- Metal Vertex Shader warning is being thrown when creating a VR Template Project
- Asset database warning is thrown when declaring font variable in the USS text file
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.