Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.38f1
2022.3.28f1
6000.0.2f1
Issue ID
UUM-71692
Regression
No
"The same field name is serialized multiple times in the class or its parent class" error is thrown when private variables are declared in the class and its parent class using underscore
How to reproduce:
1. Open the user-attached project “BugReport”
2. Open the “SampleScene” scene
3. Open the “Derived.cs” Asset and add a commented line to trigger the recompilation
4. Observe the Console
Expected results: There are no errors in the Console
Actual result: “The same field name is serialized multiple times in the class or its parent class. This is not supported: Base(Derived) _privateData” error is thrown into the Console
Reproducible with: 2021.3.38f1, 2022.3.28f1, 6000.0.2f1
Reproducible on: Windows 11 Pro, Windows 10 (user’s)
Not reproducible on: No other environment tested
Notes:
-Clicking “Reimport” on the Script doesn’t make the error appear
-Changing the name of the variable in one of the Scripts doesn’t make the error go away
Workaround:
-Deleting the underscore of one of the variables and saving and adding it back solves the issue. However, it reappears after restarting Unity
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
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.