Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.38f1
2022.3.30f1
6000.0.3f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
Issue ID
UUM-72447
Regression
No
Serialized variable value is overwritten on the existent object instead of creating a new one when using JsonUtility.FromJsonOverwrite
How to reproduce:
1. Open the user-attached project “SRJsonTest”
2. Open the “SampleScene” scene
3. Enter the Play Mode
4. Observe the last log in the Console
Expected results: The value is logged into the Console
Actual results: “Null” is logged into the Console
Reproducible with: 2021.3.38f1, 2022.3.30f1, 6000.0.3f1
Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested
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
- Query Builder items display raw code style names instead of human readable labels in search field
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
- Solid gray or black areas are present when using ShaderGraph with Custom Function nodes without manual reimport
- The Multiplayer Play mode tool doesn't see the list of Play Mode scenarios when using 6000.3.x
- Input field does not update when selecting the same input field after previous input was canceled
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.
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.