Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.3.12f1
Issue ID
1157137
Regression
No
[Android][iOS][Scripting] ToString function is not culture-variant on Android devices, and iOS 12 and higher
How to reproduce:
1. Open the attached project
2. Make sure that scripting backend is set to .NET 4.x
3. On Android device go to settings and set Region/Language/Locale to French
4. Build and run to an Android device
5. Click on "Press Me!" button
Expected result: the button text changes to '4,5' (notice the comma)
Actual result: the button text changes to '4.5' (notice the full stop)
Reproduced with: 2017.4.0f1, 2018.4.1f2, 2019.3.0a5
* works as expected on:
- Standalone (Mac, Linux, Windows) all versions
- iOS devices from 2018.3.12f1 (result on 2018.3.11f1 is '4.5' meaning no culture-variance)
* to test against other platforms, follow the same steps - set the region to French, enter Play mode and press the button
Android devices tested:
Lge Nexus 5 (Nexus 5), Android 6.0.1, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
Samsung Galaxy Note9 (SM-N960U), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Meizu - (MX5), Android 5.0.1, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
Huawei P20 Pro (CLT-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
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
- Reference to a deleted GameObject becomes "None" instead of "Missing" when the GameObject is restored with undo after entering and exiting Play Mode
- Size value in Particle System Curve's tab is highlighted with selection across all tab header
- Particle System Curve's Presets window has no visual indication of what preset is selected
- Blur shader doesn't work when the "Scene Color" Node is attached to the UI "Output" Node
- Particle System Curve presets can't be scrolled and some of them can't be selected if window is too narrow to fit them all
Resolution Note (fix version 2019.3):
Fixed in 2020.1.0a5