Search Issue Tracker
Fixed in 2021.2.X
Votes
2
Found in
2019.4
2020.3
2020.3.7f1
2021.1
Issue ID
1338524
Regression
No
A Unsupported Type error is printed when a Managed Reference replaces another that has a field with the same name
How to reproduce:
1. Open the attached project "SerializeReferenceError.zip"
2. Select 'New SR Bug Reproducer' in the Project View
3. Click Int Container in the Inspector
4. Click Compound Object Container
5. Observe Console
Expected result: Nothing is printed to the Console
Actual result: A Unsupported Type error is printed to the Console
Reproducible with: 2019.4.28f1, 2020.3.11f1, 2021.1.10f1, 2021.2.0a17
Not reproducible with: 2021.2.0a18, 2021.2.0a19
Could not test with: 2018.4.34f1 (No SerializeReference)
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note (fix version 2021.2):
Does no longer reproduce with: 2021.2.0a18. The SerializeReference code has had an extensive reworking in that release, including API and persistence format changes, which makes backporting a specific fix for this scenario into older versions difficult.