Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.3.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2018.3.7f1
Issue ID
1133961
Regression
No
System.Globalization.CultureInfo.CurrentCulture returns Invariant Culture in Players which Scripting Backend are IL2CPP
To reproduce:
1. Download attached project "CurrentCultureBug.zip" and open in Unity
2. Open "CultureBug" scene
3. Enter to Play mode
4. Observe that under Current Culture it lists your current Culture properly
5. Exit Play mode
6. Change Scripting Backend to IL2CPP
7. Build and Run for Standalone or iOS
Expected results: In Standalone or iOS under Current Culture it lists your current Culture properly
Actual results: Observe that in Standalone or iOS under Current Culture it lists Invariant Culture
Notes:
- This issue cannot be reproducible on Windows Standalone with IL2CPP Scripting Backend
- Everything works as Expected if Scripting Backend is Mono
- Cannot check earlier Unity versions because Build Process always fails or Project becomes corrupted
Reproduced on Unity 2018.2.20f1, 2018.3.8f1, 2019.1.0b6 and 2019.2.0a8
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
emagein3d
Feb 14, 2020 08:35
Issue does also exists on 2018.4.12f. Try to install last LTS 2018.4.17f to see if it's corrected