Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.0f1
2021.2
2022.1
Issue ID
1350023
Regression
No
List of Serializable classes is not Serialized when these classes are inherited from a Non-Serializable class
How to reproduce:
1. Open the "case_1350023" project
2. Open the "SampleScene" Scene
3. Comment the 46th code line in the "NewBehaviourScript.cs" script
4. Observe the "Test" GameObject's "NewBehaviourScript" Component in the Inspector
Expected result: the "Tests" and "Test" fields are visible in the Inspector under the "NewBehaviourScript" component
Actual result: only the "Test" field is visible
Reproducible with: 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a5
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note (2022.1.X):
As per documentation, Serializable attribute is required to ensure a custom class is serialized. It is true that there are still some cases where non-Serializable classes are serialized, that is permitted primarily because we do not want to cause a lot of disruption in existing code, but in future we may enforce Serializable as a requirement universally.