[
https://issues.apache.org/jira/browse/CB-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-10623.
-----------------------------
Resolution: Won't Fix
Apparently this has nothing to do with Cordova and instead is a weird Android
bug the play store has. Because of that, I'm closing this as won't fix,
because this is a Play Store bug which we have no control over.
The last stack overflow link tells you how to modify the build.gradle, but I'd
go with the checked answer of "This isn't actually a problem".
http://stackoverflow.com/questions/32076673/google-play-developer-console-shows-localizations-have-changed-in-my-apk-since-l
http://stackoverflow.com/questions/21380565/when-publishing-apk-to-google-play-some-localizations-got-removed?rq=1
http://stackoverflow.com/questions/23000604/play-store-app-localization?lq=1
> Gradle build produces APK that lists all localizations of included libraries
> ----------------------------------------------------------------------------
>
> Key: CB-10623
> URL: https://issues.apache.org/jira/browse/CB-10623
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Environment: Mac OSX, AndroidStudio, Cordova 6.0.0
> Reporter: Jacob Robbins
> Labels: localization, triaged
>
> After upgrading to Cordova 6.0.0 I built a signed APK. When I upload it to
> Google Play the publish dialog lists 78 new localizations. These
> localizations are the localizations of the libraries Google Play Services and
> Google Compat. I have no localizations, just a default (English) set of
> strings. So the Gradle build process is causing my app to incorrectly list
> localizations it does not have.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
