Search Issue Tracker
Won't Fix
Under Consideration for 2023.2.X
Votes
2
Found in
2021.3.29f1
2022.3.7f1
2023.1.8f1
2023.2.0b4
2023.3.0a1
6000.0.0b1
Issue ID
UUM-45659
Regression
No
“Unsupported type LocalizedString” error appears when modifying a LocalizedString inside a serialized object that’s inside a list which is inside a scriptable object
How to reproduce:
1. Open the user’s attached “repro.zip” project
2. In the Hierarchy, select “BrainControl” GameObject
3. In the Inspector/Debug window, go to “Progression Driver” Component
4. Select any of the elements and press the “-“ button to remove it
5. Observe the result
Expected result: No errors
Actual result: “Unsupported type LocalizedString” error appears
Reproducible with: 2021.3.29f1, 2022.3.7f1, 2023.1.8f1, 2023.2.0b4
Reproduced on: macOS 13.4.1 (Intel)
Notes:
-the issue is also reproducible when instead of the 4th step:
changing any field of the element (ex. “Comparison”)
changing the number of “Quests”
closing “LocalizationDrawer”
applying “Quests” to Prefab
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.