Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.43f1
2021.3.16f1
2022.2.2f1
2023.1.0a24
Issue ID
UUM-22520
Regression
No
Prefab overrides not saved properly when using a Script containing a list of custom class objects while using the "SerializeReferece" and "HideInInspector" attributes
How to reproduce:
1. Open the user attached project “PrefabIssueReproProject.zip”
2. Open Scene “SampleScene“ (Assets/Scenes)
3. Select the “MainObject” GameObject in the Hierarchy
4. Select the context menu of “MainScript” in the Inspector
5. Press "Add item"
6. Select the “Main Script” Component's context menu
7. Select “Modified Component” and press "Apply to prefab 'MainObject'"
Expected result: The prefab changes are saved
Actual result: Changes are reverted and "Destination property underlying types does not match the given one" error is thrown in the Console
Reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a24
Reproduced on: macOS 13.0.1 (Intel)
Notes:
- When selecting "Add item" in prefab isolation mode, the list changes, but the prefab changes are not registered
- Unable to reproduced when removing the “HideInInspector” attribute
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
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.1.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.