Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2020.3.46f1
2021.3.22f1
2022.2.12f1
2023.1.0b10
2023.2.0a8
2023.3.0a3
Issue ID
UUM-31370
Regression
No
Console throws Unsupported enum type errors when enum inherits from type "long"
Reproduction steps:
1. Open the attached "repro_IN-36180EnumSerialization.zip" project
2. Open the “Assets/Scenes/SampleScene” Scene
4. Open the Console window and observe the error messages
Expected result: No error messages are produced
Actual result: Unsupported enum type error messages are produced
Reproducible with: 2020.3.46f1, 2021.3.22f1, 2022.2.12f1, 2023.1.0b10, 2023.2.0a8
Reproducible on: Windows 10
Note: reproducible with any access modifier
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
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 (2023.3.X):
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.