Build 1142 adds new languages/localization to the apk?

Solar2D Daily Builds and Public Releases
#1

Hi,

I’ve just uploaded apk built with 1142, and Google Play Store reports changes in localization. Previously it was only “default” and now I’ve got these three added:

  • spanish – es
  • hebrew – iw
  • hebrew – iw

Since I didn’t change anything in my app [I’m testing one of the cases you fixed after public release] I assume there was something added to the build process.

Should I raise a case?

Thanks

Krystian

#2

Hi @Krystian,

I brought this issue up to the engineers and they’ll tell me if there’s reason for concern.

Thanks,

Brent

#3

Hi Krystian,

Here’s the report I received from the engineers:

“Regarding Android localization, you do not need to modify the “build.settings” file or the “AndroidManifest.xml” file to support different locales. When displaying the Google Play in-app purchase dialog, it is supposed to be displayed in the language/locale that the device is set up for as well as the localized prices that you’ve set up in the Google Play Developer Console.”

Does this help?

Best regards,

Brent

#4

Hello Brent,

not really.

I don’t have anything in configuration files which would suggest any localization [i set it up in google play store dev console].

Like I mentioned. I have changed nothing in my code base between 1137 and 1142. It was a rebuild, yet play store showes this change.

Here’s my build.settings:

-- Supported values for orientation: -- portrait, portraitUpsideDown, landscapeLeft, landscapeRight settings = { orientation = { default = "portrait", supported = { "portrait", "portraitUpsideDown"} }, iphone = { plist = { CFBundleDisplayName = "bundle name", UIStatusBarHidden = true, UIPrerenderedIcon = true, -- set to false for "shine" overlay UIApplicationExitsOnSuspend = false, FacebookAppID = "123", UIAppFonts = { "EngrvrsOldEngEU-Bold.ttf", "EngrvrsOldEngEU-Normal.ttf", "Roboto-Regular.ttf", "Insula.ttf", }, CFBundleURLTypes = { { CFBundleURLSchemes = { "fb123", -- replace 00000000000 with your facebook appId } } }, CFBundleIconFiles = { "Icon.png", "Icon@2x.png", "Icon-72.png", "Icon-72@2x.png", "Icon-Small-50.png", "Icon-Small-50@2x.png", "Icon-Small.png", "Icon-Small@2x.png", }, } }, android = { largeHeap = true, usesExpansionFile = true, usesPermissions = { "android.permission.ACCESS\_WIFI\_STATE", "android.permission.VIBRATE", "android.permission.INTERNET", "com.android.vending.CHECK\_LICENSE", "android.permission.WRITE\_EXTERNAL\_STORAGE", "android.permission.READ\_PHONE\_STATE", "android.permission.ACCESS\_NETWORK\_STATE", "com.android.vending.BILLING", }, }, }
#5

Hi Krystian,

I asked the engineers again, and they state that nothing was changed on our end. In-app purchases for different locales is configured via the Google Play developer console, not the Android app. There is nothing in the Android app that can trigger it. Please check again in your Google Play developer console and see what’s reported there for the IAP items. That’s about all I can suggest at this time.

Thanks,

Brent

#6

Hi @Krystian,

I brought this issue up to the engineers and they’ll tell me if there’s reason for concern.

Thanks,

Brent

#7

Hi Krystian,

Here’s the report I received from the engineers:

“Regarding Android localization, you do not need to modify the “build.settings” file or the “AndroidManifest.xml” file to support different locales. When displaying the Google Play in-app purchase dialog, it is supposed to be displayed in the language/locale that the device is set up for as well as the localized prices that you’ve set up in the Google Play Developer Console.”

Does this help?

Best regards,

Brent

#8

Hello Brent,

not really.

I don’t have anything in configuration files which would suggest any localization [i set it up in google play store dev console].

Like I mentioned. I have changed nothing in my code base between 1137 and 1142. It was a rebuild, yet play store showes this change.

Here’s my build.settings:

-- Supported values for orientation: -- portrait, portraitUpsideDown, landscapeLeft, landscapeRight settings = { orientation = { default = "portrait", supported = { "portrait", "portraitUpsideDown"} }, iphone = { plist = { CFBundleDisplayName = "bundle name", UIStatusBarHidden = true, UIPrerenderedIcon = true, -- set to false for "shine" overlay UIApplicationExitsOnSuspend = false, FacebookAppID = "123", UIAppFonts = { "EngrvrsOldEngEU-Bold.ttf", "EngrvrsOldEngEU-Normal.ttf", "Roboto-Regular.ttf", "Insula.ttf", }, CFBundleURLTypes = { { CFBundleURLSchemes = { "fb123", -- replace 00000000000 with your facebook appId } } }, CFBundleIconFiles = { "Icon.png", "Icon@2x.png", "Icon-72.png", "Icon-72@2x.png", "Icon-Small-50.png", "Icon-Small-50@2x.png", "Icon-Small.png", "Icon-Small@2x.png", }, } }, android = { largeHeap = true, usesExpansionFile = true, usesPermissions = { "android.permission.ACCESS\_WIFI\_STATE", "android.permission.VIBRATE", "android.permission.INTERNET", "com.android.vending.CHECK\_LICENSE", "android.permission.WRITE\_EXTERNAL\_STORAGE", "android.permission.READ\_PHONE\_STATE", "android.permission.ACCESS\_NETWORK\_STATE", "com.android.vending.BILLING", }, }, }
#9

Hi,

I have the same problem. May I know if it is googlePlay’s problem or the SDK problem? I did a search but can’t find any other similar case except this thread. 

GooglePlay shows these three extra language

  • spanish – es
  • hebrew – iw
  • hebrew – iw

Build with version 1154

Nothing changes from previous build, just want to update Apps for Nook.  It is a PAID app with no IAP at all.

Thanks in advance

#10

Hi Nob Studio,

good to know I’m not the only one.

I just think that the interest in android development among pro users is ver small. If there are few people using corona for Android they seem not to notice the languages  added.

It is a corona issue, I’ve double checked with previous builds and nothing like that happened.

I only have few testers currently and none of them use spanish or hebrew language, so I’m not sure if this change has any impact on users, but I would feel a bit cheated if someone promised me a localized product [especially if it is paid, like in your case] and would not deliver.

#11

Hi all,

I have an official answer for you. The reason the Spanish and Hebrew languages are now listed as “supported” under Google Play is because we’ve upgraded to the newest version of the Facebook SDK on Android, which includes support for those languages. But just because those languages are listed as supported under the “localizations” list does not mean Google Play will distribute your app in those countries… you would actually have to opt-in to those countries under the “Pricing and Distribution” section.

Hope this helps,

Brent

#12

Brent: but it means google play users will see that developer marked their app as localized in these languages.

This is kind of a lie.

#13

Hi Krystian,

Perhaps I’m missing something: where is the localization specified on the Google Play page for an app?

For example, Angry Birds:

https://play.google.com/store/apps/details?id=com.rovio.angrybirds&hl=en

#14

As far as I’ve seen, Google Play does not list what languages an app supports to end-users.  For example, check out Angry Birds on Google Play…

   https://play.google.com/store/apps/details?id=com.rovio.angrybirds

The newest Facebook SDK for Android now provides dialogs that can be displayed within your app and that dialog supports the languages that you’ve listed above (including English of course).  So, if the device is set up under a Spanish or Hebrew locale, then the Facebook dialog will display text with that language.

On Google Play, you have to opt-in to what countries you plan on distributing your app to.  You do this in the Google Play Developer Console under the “Pricing and Distribution” section of that website.  This will generate a localized version of your Google Play app webpage… not the locales/languages that your app supports.  So, you shouldn’t have anything to worry about.

#15

Here’s on samsung apps:

http://apps.samsung.com/venus/topApps/topAppsDetail.as?productId=000000521404&srchClickURL=|@sn=SAPS|@qh=-1579003731|@qid=SAPS.SRCH|@q=angry|@tot=56|@idx=0|@doc=G00010328791|@title=nil#

Yup, can’t see it on google play, although I am sure it was there in previous versions of the store.

#16

Can you not edit the app’s information on Samsung’s app store?

#17

Hello Joshua,

I cannot make any changes to my existing app, but when uploading new one I will be sure to check it out.

Thanks,

K

#18

Here’s my perspective.  It’s actually normal for 3rd party libraries to include translated resources.  Because of this, it would be bad of the app store to assume that the entire app supports a language just because it happens to find one translated resource within the app.  Google Play appears to handle this correctly.  I think the Google Play Developer Console is just listing out the languages it has discovered within the APK to help those developers who upload multiple localized APKs… especially for apps that have localized image and audio files because that would cut down on the APK file size for different regions.

Native Android developers would typically accept 3rd party libraries such as Facebook as-is, including the localized resources, without modifying them.  If the rest of the native Android development world doesn’t have a problem with this, I don’t see any reason why we should either.

But that said, I am interested to know if the Samsung app store allows you to control the languages supported on the app store page.  I personally don’t have a Samsung developer account to check this out for myself.  So, if you can let me know then that would be great.

#19

Hi Krystian,

I asked the engineers again, and they state that nothing was changed on our end. In-app purchases for different locales is configured via the Google Play developer console, not the Android app. There is nothing in the Android app that can trigger it. Please check again in your Google Play developer console and see what’s reported there for the IAP items. That’s about all I can suggest at this time.

Thanks,

Brent

#20

Hi,

I have the same problem. May I know if it is googlePlay’s problem or the SDK problem? I did a search but can’t find any other similar case except this thread. 

GooglePlay shows these three extra language

  • spanish – es
  • hebrew – iw
  • hebrew – iw

Build with version 1154

Nothing changes from previous build, just want to update Apps for Nook.  It is a PAID app with no IAP at all.

Thanks in advance