Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.1.1
Issue ID
LOC-627
Regression
No
unexpected error with empty specific locale selector and a valid project locale identifier
Reproduce steps
- Go to localization setting
- Select none for specific locale selector
- Select a valid project locale identifier
Actual result: error thrown : no locale could be selected
Expected result: Project locale identifier is being used as default locale.
!https://media.github.cds.internal.unity3d.com/user/3869/files/922d864b-78f3-480e-b81d-f65dc0d5db66!
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
The project locale is part of localized property variants. Its the locale value we store in the object instead of as a variant. We always need a selected locale.