Search Issue Tracker
Fixed
Fixed in 1.3.1
Votes
0
Found in [Package]
1.1.1
Issue ID
LOC-601
Regression
No
Errors are thrown in Play Mode when Project Locale Identifier is not set in Localization Settings
How to reproduce:
1. Open the user's attached project
2. Open scene Main
3. Press the Play button and observe the Console
Expected result: no errors related to Locale are thrown
Actual result: errors related to Locale are thrown
Reproducible with: 1.0.0, 1.1.1 (2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a5)
Notes:
1. On 2019.4 and 2020.3, the error thrown is "No locale could be selected <...>"
2. On 2021.2 onward, the error thrown is NullReferenceException
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