Search Issue Tracker

Active

Under Consideration for 1.5.X

Votes

0

Found in [Package]

1.5.2

Issue ID

LOC-1162

Regression

No

[Android] Incorrect List of supported languages on Android

Package: Localization Package

-

Was asked to process the ticket without having a local reproduction: [https://unity.slack.com/archives/C0PSRQXDZ/p1728368156763019|https://unity.slack.com/archives/C0PSRQXDZ/p1728368156763019|smart-link]

----

1. What happened
[https://discussions.unity.com/t/is-it-important-to-have-localisation-settings-for-android-correct/915634/3|https://discussions.unity.com/t/is-it-important-to-have-localisation-settings-for-android-correct/915634/3]
karl_jones asked to report this as a bug.

Since the first build for Android using Unity, when uploading the build to Google Play Console, their system would identify supported languages. As I asked, I am unsure if this is really an issue. But since ASO must use this information, it probably is an issue. The first build did not have localization but was showing that we supported 85 languages. After adding the localization package with 5 languages, it now shows that we support 89 languages on the Google Play Console.

karl_jones suggested that we should delete folders that would have these languages, but they do not exist. So I am unclear where these 85 languages are coming from. He then suggests that the problem might be that the localization package is adding languages, but not removing languages that were once added, and therefore asked to report a bug.

2. How can we reproduce it using the example you attached

* Create an AAB with Unity without the localization package.
* Upload it to Google Play Console to check the amount of languages (it should show 85).
* Add the localization package and add a couple of languages in the metadata
* Create another AAB and upload to Unity to see if the supported languages has increased. The bug is that it is showing more the 85, instead of just the amount of languages added on the localization package.

I am guessing here, that if we start a project with the localization package installed, this might not happen and it will show the correct amount of languages supported. But since we already have made a build without the package, it is not deleting the languages that were added before, as per karl_jones comment.

Add comment

Log in to post comment