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
- Files in the target folder are deleted without a proper warning when building an iOS project
- Character animation freezes when toggling animator on/off in a coroutine
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
Add comment