Search Issue Tracker
Fixed
Votes
0
Found in [Package]
0.10.0-preview
Issue ID
LOC-150
Regression
No
Inconsistent behaviour between LocaleIdentifier constructors and deserialization when using different empty instances
Inconsistent behaviour between LocaleIdentifier constructors and deserialization when using the default, empty string, serialized "None" and "LocaleIdentifier.Undefined" instances
Reproduction steps:
1. Open the user's attached project and Scenes/SampleScene scene
2. Enter the Play mode
3. Observe the Console window
Expected result: All the instances are equal and/or are equal to "LocaleIdentifier.Undefined"
Actual result: Only the "fromEmtpyString" is equal to "LocaleIdentifier.Undefined", whereas any other combination is unequal
Reproducible with: 0.7.1-preview - 0.10.0-preview (2019.4.20f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a3)
Could not test with: 2018.4.31f1 (could not downgrade Localization package)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment