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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment