[jira] [Updated] (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:all-tabpanel
]
Josh Kasten updated CB-10014:
-
Description:
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}
{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.
was:
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}
{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 apps 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 will be the same.
This is silent issue to the developer as it only becomes an issue when the end
user installs 2 apps built this way. This issue should be addressed quickly to
prevent issues when developers release their APK or provide a work for plugin
developers to add something to their plugin.xml to default in a applicationId.
Thanks.
> 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}
> 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-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (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:all-tabpanel
]
Josh Kasten updated CB-10014:
-
Description:
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}
{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 apps 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 will be the same.
This is silent issue to the developer as it only becomes an issue when the end
user installs 2 apps built this way. This issue should be addressed quickly to
prevent issues when developers release their APK or provide a work for plugin
developers to add something to their plugin.xml to default in a applicationId.
Thanks.
was:
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
```
```
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 apps 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 will be the same.
This is silent issue to the developer as it only becomes an issue when the end
user installs 2 apps built this way. This issue should be addressed quickly to
prevent issues when developers release their APK or provide a work for plugin
developers to add something to their plugin.xml to default in a applicationId.
Thanks.
> 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
>Priority: Critical
> 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}
> 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 apps 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 will be the same.
> This is silent issue to the developer as it only becomes an issue when the
> end user installs 2 apps built this way. This issue should be addressed
> quickly to prevent issues when developers release their APK or provide a work
> for plugin developers to add something to their plugin.xml to default in a
> applicationId.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (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:all-tabpanel
]
Joe Bowser updated CB-10014:
Priority: Major (was: Critical)
> 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}
> 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 apps 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 will be the same.
> This is silent issue to the developer as it only becomes an issue when the
> end user installs 2 apps built this way. This issue should be addressed
> quickly to prevent issues when developers release their APK or provide a work
> for plugin developers to add something to their plugin.xml to default in a
> applicationId.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
