Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.1f1
2022.2.0b5
2023.1.0a6
2023.2.0a1
Issue ID
UUM-1031
Regression
No
Value of a serialized class is reverted when Component is applied to a Prefab after the value is set to null
Reproduction steps:
1. Open the attached Project "Case_1423203.zip" and load Scene "SampleScene"
2. Select the "Test" GameObject in the Hierarchy
3. Right-click the Component "Test" in the Inspector and click "foo = null" in the Context Menu
4. Right-click the Component "Test" in the Inspector and click "Modified Component -> Apply to Prefab 'Test'"
Expected result: Foo remains null
Actual result: Foo is reverted back to its previous state and "Could not apply data updates at destination property with path 'foo'" error is thrown in the Console
Reproducible with: 2021.3.1f1, 2022.1.0f1, 2022.2.0a11
Not reproducible with: 2019.4.38f1, 2020.3.34f1 ("The list of \[SerializeReference] objects being deserialized is from a more recent version of Unity. This is not supported and objects will be skipped." error is thrown)
Notes:
- Applying the changes through the Prefab Overrides menu prevents the issue from reproducing
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
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.