[
https://issues.apache.org/jira/browse/CB-10014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067211#comment-15067211
]
ASF GitHub Bot commented on CB-10014:
-------------------------------------
GitHub user dpogue opened a pull request:
https://github.com/apache/cordova-android/pull/247
CB-10014: Set gradle applicationId to package name.
This fixes an issue that's affecting several Cordova Android apps where
Google Play services causes conflicts that prevent multiple apps from being
installed.
JIRA issue: https://issues.apache.org/jira/browse/CB-10014
See also: https://code.google.com/p/android/issues/detail?id=193567
http://tools.android.com/tech-docs/new-build-system/applicationid-vs-packagename
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dpogue/cordova-android gradle-appId
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-android/pull/247.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #247
----
commit de1644068b22c10af6a20566ec142e22590205d2
Author: Darryl Pogue <[email protected]>
Date: 2015-12-21T22:53:49Z
CB-10014: Set gradle applicationId to package name.
----
> Gradle variable applicationId is not set, creates issue with Google Play
> services 8.3.0
> ---------------------------------------------------------------------------------------
>
> Key: CB-10014
> URL: https://issues.apache.org/jira/browse/CB-10014
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 5.4.1
> Reporter: Josh Kasten
> Labels: android, gradle
>
> applicationId is not set in build.gradle which creates an issue with
> com.google.android.gms:play-services-measurement:8.3.0. This aar file has the
> following line in AndroidManifest.xml
> {code:xml}
> <provider
> android:authorities="${applicationId}.google_measurement_service"
>
> android:name="com.google.android.gms.measurement.AppMeasurementContentProvider"
> android:exported="false"/>
> {code}
> applicationId becomes `com.google.android.gms.measurement` when the manifest
> entry is merged since applicationId is not set in the main project .gradle
> file. This means that if another app also includes the Google Play services
> library 8.3.0 it will fail to install on the device with an
> INSTALL_FAILED_CONFLICTING_PROVIDER error because the name isn't unique.
> This is silent problem to developers as it only becomes an issue when the end
> user installs 2 apps built this way. This should be addressed quickly to
> prevent this error when developers release their APK or provide a work around
> for plugin developers to add something to their plugin.xml to default in the
> applicationId gradle variable.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
