Search Issue Tracker
Won't Fix
Votes
2
Found in
2021.3.40f1
2022.3.37f1
6000.0.10f1
Issue ID
UUM-76439
Regression
No
JsonSerialization.ToJson serializes "$type" when serializing Dictionaries
How to reproduce:
1. Open the “Test.zip“ project
2. Open the “Playground“ Scene
3. Enter Play Mode
4. Observe the Console
Expected result: The Console log reads:
”{ "Single": {},
"List": [ {} ],
"Set": [ {} ],
"Dict": { "Item": {} }
}”
Actual result: The Console log reads:
”{ "Single": {},
"List": [ {} ],
"Set": [ {} ],
"Dict": { "Item": { "$type": "BugReproduction.Item, Assembly-CSharp" } }
}”
Reproducible in: 2021.3.40f1, 2022.3.37f1, 6000.0.10f1
Reproduced on: Windows 11 Pro (23H2)
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
- Polyspatial Material swap set animations are not firing when used in Play Mode and Players
- Incomplete shortcuts are displayed in the "Set" dropdown in Visual Effects Graph VFX Control subwindow
- Version change sub-window closes automatically when "Add Modules" subwindow is closed
- RenderTexture content from 'Depth Only' camera is not rendered correctly on UI RawImage when Multithreaded Rendering is enabled on specific MediaTek devices.
- Weight Brush Overlay text is clipped in Sprite Editor
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.