Search Issue Tracker
By Design
Votes
0
Found in
2019.2.12f1
2020.1
Issue ID
1201983
Regression
No
[Android] Application.systemLanguage does not update after changing language while application is in background
To reproduce:
1. Open attached project
2. Build and run to android device
3. Open the application and press the "Check system language" button ( shows language that is used at the moment)
4. Put application to the background and go to the system settings
5. Change the system language to another one
6. Open the application from the background and press the button again
Actual result: The application does not update the language that was changed in system settings while the application was in the background
Expected result: The language should be updated while the application was minimized
Reproduced with: 2019.2.15f1; 2020.1.15f1
Can not check on lower versions due to packages errors.
Tested and reproduced with:
VLNQA00170, Google Pixel 2 (Pixel 2), Android 10, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Crashes on iPhone 7+ (iOS 11.4.1) when changing the system language. (seems like iOS kills the app while changing the system language)
Note: If the application is killed and reopened the Application.systemLanguage updates the language.
Logcat attached
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
There is no way to fix this, Locale is set for JVM during startup and it cannot be updated without restart.
https://developer.android.com/reference/java/util/Locale.html#getDefault(java.util.Locale.Category)
Theoretically we can listen to https://developer.android.com/reference/android/content/Intent.html#ACTION_LOCALE_CHANGED event, and then restart app, but I don't think that this is what our users want.