Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.40f1
2022.3.36f1
6000.0.9f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
7000.0.0a1
Issue ID
UUM-75197
Regression
No
The serialized custom class declaration set to null gets instanced once and then returns to the null state when entering the Play Mode with the Domain Reloading enabled
How to reproduce:
1. Open the “Repro_stripped“ project
2. Open the “SampleScene“
3. Enter the Play Mode
4. Observe the Console window
Expected result: The “OnAfterDeserialize: test is not null“ message is not logged
Actual result: The “OnAfterDeserialize: test is not null“ message is logged once
Reproducible with: 2021.3.40f1, 2022.3.36f1, 6000.0.9f1
Reproducible on: macOS 14.5 (Intel), Windows 11 (User’s)
Not reproducible on: No other environments tested
Workaround: Add the [field: NonSerialized] attribute to the “_test“ field in the “Foo.cs“ script
Note: For the issue to be reproducible the Domain Reloading must be enabled
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
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.