What does this error message mean? I don't have duplicated packages in my project
Error:Execution failed for task ':SimpleReader:processDebugResources'.
Error: more than one library with package name 'com.google.android.gms'
You can temporarily disable this error with android.enforceUniquePackageName=false However, this is temporary and will be enforced in 1.0
My build.gradle
looks like this:
buildscript {
repositories {
maven { url 'http://repo1.maven.org/maven2' }
mavenCentral()
}
dependencies {
classpath 'com.android.tools.build:gradle:0.9.1'
}
}
apply plugin: 'android'
android {
buildToolsVersion '19.0.3'
defaultConfig {
minSdkVersion 14
targetSdkVersion 17
}
compileSdkVersion 17
packagingOptions {
exclude 'META-INF/DEPENDENCIES'
exclude 'META-INF/NOTICE'
exclude 'META-INF/LICENSE'
exclude 'META-INF/LICENSE.txt'
exclude 'META-INF/NOTICE.txt'
}
buildTypes {
}
}
dependencies {
compile 'com.android.support:support-v4:19.0.1'
compile 'com.google.android.gms:play-services:4.2.42'
compile files('libs/gson-2.2.4.jar')
compile files('libs/httpmime-4.1.jar')
compile files('libs/httpclient-4.1.1.jar')
compile files('libs/jsoup-1.7.3.jar')
compile project(':libraries:actionbarsherlock')
compile project(':libraries:sherlocknavigationdrawer')
compile project(':libraries:googleplayservices')
compile project(':libraries:androidslidinguppanel')
compile files('libs/protocol-1.0.4.jar')
compile files('libs/sentry-0.1.4.jar')
compile files('libs/commons-lang-2.3.jar')
}
I faced similar issue, i got it resolved by following steps:
ionic platform rm android
ionic platform add android
ionic build android
Try removing
compile project(':libraries:googleplayservices')
orcompile 'com.google.android.gms:play-services:4.2.42'
. I am pretty sure they are the same library.I had confused with this problem for a long time.My issue is little different with the question though same error log. I want my sublib's buildtype same with my application's buildtype. So I assigned the buildtype for sublib as the document tells me. [Gradle Plugin User Guide][1]
This the error I got.
processing flavorCustomResource
Error: more than one library with com.xxx.libCommon
This is my structure. lib1 and lib2 are independent of each other.
app
-> lib1 -> libCommon
-> lib2 -> libCommon
I got the error only when I build my custom buildtype.However, The release version was Ok.
More details. some parts of my build.gradle
app:
lib1:
lib2
Solution: configure the lib2 as lib1. the problem will be solved.
lib2:
Reason
The problem is something about Library Publication
The default publish is release. if lib2 is not configured, it will use the default publish libCommon(release version) which is different from lib1 -> libCommon(custom version) assigned by lib1's build.gradle.This comes the error.
I wish my post will help someone struggle with the same issue or give some hint to him/her.
today I met the same problem. I need to use Google Analytics, so I import google analytics lib following the tutorial:
then compile the project, gradle tell me
Error: more than one library with package name 'com.google.android.gms'
I can definitely sure that I only directly import
com.google.android.gms
one time bygoogle analytics
lib.so I navigate to
Project
tab in Android Studio to see what are the libs this project depend on, then I foundplay-services-6.5.87
display inExternal Libraries
, like following screenshot:so now I know there is another lib depend on
play-services-6.5.87
, but I don't which lib it is.then I use a gradle command in console to see the project dependencies:
the result tells me that
com.facebook.android:audience-network-sdk:4.6.0
depend on it.so how we fix this problem, two way:
audience-network-sdk
, just remove it. my project in fact doesn't need it.if you also need
audience-network-sdk
andgoogle-analytics
, useexclude group
grammar, like following snippet code.in your case, the
audience-network-sdk
can be any other lib that depends on same lib with other libs. here is just a thinking of how to resolve similar problems.In my case, the problem was because I was including:
both the wearable play services, and the regular. I commented out the wearable part, and it works.
Not sure if I'll need it, but it was included by default by the project wizard
this is a problem with versions. if you have multiple dependencies of same package path ensure the versions are the same