You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Tal Moshayov (JIRA)" <ji...@apache.org> on 2015/12/03 11:28:11 UTC

[jira] [Commented] (CB-10014) Gradle variable applicationId is not set, creates issue with Google Play services 8.3.0

    [ https://issues.apache.org/jira/browse/CB-10014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037618#comment-15037618 ] 

Tal Moshayov commented on CB-10014:
-----------------------------------

+1 on this one. took me days to understand what's going, as [~Bnaya] mentioned - only luck will get you to this thread, which contains the only workaround I found on the web.
This issue is already shows signs of an epidemic. I saw 2 apps already that failed to install with INSTALL_FAILED_CONFLICTING_PROVIDER on different phones. This means that there are already apps that have been deployed with the default `android:authorities` and will block future apps from installing. 


> 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: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org