How to exclude duplicate native library from Gradle project dependency? - android

I have two Gradle modules for Android, one is a library and one is an application, and the application has a dependency on the module, like so: compile project(path ':library' configuration: 'debug')
The problem is that both modules use JNI, so they both packagelibc++_shared.so
from the NDK, causing:
com.android.build.api.transform.TransformException:
com.android.builder.packaging.DuplicateFileException:
Duplicate files copied in APK lib/armeabi-v7a/libc++_shared.so
I tried using packagingOptions, but it seems like I can only use that to completely exclude that file from being packaged at all, not just from being copied from the other module?

What type of packagingOptions have you tried to use? Probably, exlude? It looks like pickFirst should work for you. In this case you explicitly tell Gradle that you know about the problem and accept any of these files. Depending on the architectures you support you may need only some of the lines. You can find details in documentation
android {
// some stuff
packagingOptions {
pickFirst 'lib/armeabi-v7a/libgnustl_shared.so'
pickFirst 'lib/arm64-v8a/libgnustl_shared.so'
pickFirst 'lib/x86_64/libgnustl_shared.so'
pickFirst 'lib/x86/libgnustl_shared.so'
}
}

Related

Duplicate files copied in APK lib/x86/librealm-jni.so - Conflict with cache in ~/.gradle/cache

The app builds successfully but while running, i get the following error:
Duplicate files copied in APK lib/x86/librealm-jni.so
File1: /Users/apple/.gradle/caches/modules-2/files-2.1/io.realm/realm-android/0.87.1/6d9a1bba4e31252cc8183aa27a32e6edbdacaeb7/realm-android-0.87.1.jar
File2: /Users/apple/NodeProjects/react-native-mod/droid/databinder/build/intermediates/bundles/default/jni
When I remove the realm dependency from databinder module, it cannot find the lib.
How do I remove the cached version of jar file from adding into the APK?
Add below into your gradle.build file
packagingOptions {
pickFirst 'lib/x86/librealm-jni.so'
pickFirst 'lib/x86_64/librealm-jni.so'
pickFirst 'lib/armeabi/librealm-jni.so'
pickFirst 'lib/armeabi-v7a/librealm-jni.so'
pickFirst 'lib/arm64-v8a/librealm-jni.so'
}
This option will only pick up the .so files when it is firstly seen by the build system and ignore all the subsequent same .so files.

How to exclude transitive native libraries?

Let's say my project is dependent on two libraries A and B. These libraries are dependent on the same version of a library C. Library C is dependent on a couple of shared library files D. To use library C, libraries A and B both include D in their jniLibs directories.
Now, the issue here is that when I attempt to build this project with the dependencies configured:
compile('group:A:1.0#aar')
compile('group:B:1.0#aar') {
exclude group: 'group', module: 'C'
}
I receive an error stating that there are duplicate D files. How can I go about informing gradle to ignore certain jniLibs from only one of my libraries? Is there an exclude analog for jniLibs transitive dependencies?
I was able to achieve this via gradle by forcing gradle to just use the first version of the shared library that it found:
android {
packagingOptions {
pickFirst 'lib/armeabi/D.so'
pickFirst 'lib/x86_64/D.so'
pickFirst 'lib/armeabi-v7a/D.so'
pickFirst 'lib/x86/D.so'
pickFirst 'lib/arm64-v8a/D.so'
}
}

More than one file was found with OS independent path 'META-INF/LICENSE'

When I build my app, I get the following error:
Error: Execution failed for task ':app:transformResourcesWithMergeJavaResForDebug'.
More than one file was found with OS independent path 'META-INF/LICENSE'
This is my build.gradle file:
apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
android {
compileSdkVersion 25
buildToolsVersion "25.0.2"
defaultConfig {
applicationId "cn.sz.cyrus.kotlintest"
minSdkVersion 14
targetSdkVersion 25
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
javaCompileOptions{
annotationProcessorOptions{
includeCompileClasspath = true
}
}
multiDexEnabled true
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
packagingOptions {
/* exclude 'META-INF/DEPENDENCIES'
exclude 'META-INF/NOTICE'
exclude 'META-INF/LICENSE'
exclude 'META-INF/LICENSE.txt'
exclude 'META-INF/NOTICE.txt'*/
}
}
dependencies {
compile fileTree(include: ['*.jar'], dir: 'libs')
androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
exclude group: 'com.android.support', module: 'support-annotations'
})
compile "org.jetbrains.kotlin:kotlin-stdlib-jre7:$kotlin_version"
compile "org.jetbrains.kotlin:kotlin-reflect:$kotlin_version"
compile 'com.android.support:appcompat-v7:25.3.1'
testCompile 'junit:junit:4.12'
compile 'com.android.support:design:25.3.1'
compile 'com.android.support.constraint:constraint-layout:1.0.2'
debugCompile 'com.squareup.leakcanary:leakcanary-android:1.5.1'
releaseCompile 'com.squareup.leakcanary:leakcanary-android-no-op:1.5.1'
testCompile 'com.squareup.leakcanary:leakcanary-android-no-op:1.5.1'
compile 'com.github.GrenderG:Toasty:1.2.5'
compile 'com.orhanobut:logger:1.15'
compile 'io.reactivex.rxjava2:rxandroid:2.0.1'
compile 'com.umeng.analytics:analytics:latest.integration'
compile 'ai.api:libai:1.4.8'
compile 'ai.api:sdk:2.0.5#aar'
// api.ai SDK dependencies
compile 'com.google.code.gson:gson:2.8.0'
compile 'commons-io:commons-io:2.4'
compile 'com.android.support:multidex:1.0.1'
}
When I add this code to my build.gradle file,
packagingOptions {
exclude 'META-INF/DEPENDENCIES'
exclude 'META-INF/NOTICE'
exclude 'META-INF/LICENSE'
exclude 'META-INF/LICENSE.txt'
exclude 'META-INF/NOTICE.txt'
}
This error would be solved, but another problem will happen. Like this:
java.lang.NoClassDefFoundError: com.squareup.leakcanary.internal.HeapAnalyzerService
at com.squareup.leakcanary.LeakCanary.isInAnalyzerProcess(LeakCanary.java:145)
at cn.sz.cyrus.wemz.TestApplication.onCreate(TestApplication.kt:32)
Who has ideas how to solve this?
You can add this in yourProject/app/build.gradle inside android{}. The exclude function adds the named resource to the list of resources that are not packaged in the APK.
android {
packagingOptions {
exclude("META-INF/DEPENDENCIES")
exclude("META-INF/LICENSE")
exclude("META-INF/LICENSE.txt")
exclude("META-INF/license.txt")
exclude("META-INF/NOTICE")
exclude("META-INF/NOTICE.txt")
exclude("META-INF/notice.txt")
exclude("META-INF/ASL2.0")
exclude("META-INF/*.kotlin_module")
}
}
The exclude function is deprecated in 7.0.2 and you should use something similar to this:
android {
...
packagingOptions {
resources.excludes.add("META-INF/*")
}
}
In my case it was enough to exclude only path 'META-INF/DEPENDENCIES' on yourProject/app/build.gradle inside android{} . Here it is
packagingOptions {
exclude 'META-INF/DEPENDENCIES'
}
And then do Clean Project and Rebuild Project.
The solutions here didn't help me, but this link did.
If you have a library that's adding some android .so files –like libassmidi.so or libgnustl_shared.so– you have to tell gradle to pick just one when packaging, otherwise you'll get the conflict.
android {
packagingOptions {
pickFirst 'lib/armeabi-v7a/libassmidi.so'
pickFirst 'lib/x86/libassmidi.so'
}
}
I was having this issue when using a React Native app as a library in an Android project.
Basically when gradle puts together the apk file, it copies content from all the compile dependencies, It is intelligent enough to see that there is a duplicate file..coming from two different jar files. This could be any file like a.txt or META-INF/DEPENDENCIES. It might be best to exclude these files using the below, in case the file is present there only for informational purposes.
android{
packagingOptions {
exclude 'META-INF/DEPENDENCIES'
}
}
Or if in case, the file is a mandatory file like a class file, that has been duplicated across two jar dependencies that are related to each other, it is best to find alternatives to these jars, in the way of a more compatible version.
I have faced a similar issue working in a multiple modules app environment:
Error: Execution failed for task
':app:transformResourcesWithMergeJavaResForDebug'. More than one file
was found with OS independent path 'META-INF/AL2.0'
This issue was being reported by several of these modules of mine and none of the above solutions were fixing it.
Turns out, I was using version Coroutines 1.3.6 which seemed to be embedding META-INF/AL2.0 which was already embedded by another of the libraries I was using. To fix it, I have added the following code snippet to the build.gradle of the module that was failing:
configurations.all {
resolutionStrategy {
exclude group: "org.jetbrains.kotlinx", module: "kotlinx-coroutines-debug"
}
}
Given that it was happening on multiple modules, I have moved that resolutionStrategy code to my project level build.gradle.
Everything worked after that.
Had similar message
Error:Execution failed for task ':app:transformResourcesWithMergeJavaResForDebug'.
More than one file was found with OS independent path 'constant-values.html'
To resolve it, I had to enable packages view(1) in Android Studio, then browse through the tree to libraries, and locate the duplicates(2)
Then, ctrl+alt+f12 (or RMB menu)(3) - and found libraries which caused the issue.
Made list of files inside those libs which caused the issues, and wrote them to app's build.gradle file inside android section. Other option is to deal with the library, containing duplicate files
packagingOptions {
exclude 'allclasses-frame.html'
exclude 'allclasses-noframe.html'
<..>
It's perfectly safe to exclude all meta-info files which are there just for documentation and information purposes:
android{
packagingOptions {
exclude 'META-INF/*'
}
}
Source: https://stackoverflow.com/a/49101232/13093413
Add the following in app level gradle file inside android{}
packagingOptions {
exclude 'META-INF/DEPENDENCIES'
exclude 'META-INF/LICENSE'
exclude 'META-INF/LICENSE.txt'
exclude 'META-INF/license.txt'
exclude 'META-INF/NOTICE'
exclude 'META-INF/NOTICE.txt'
exclude 'META-INF/notice.txt'
exclude 'META-INF/ASL2.0'
exclude("META-INF/*.kotlin_module")
}
This happens when using
org.jetbrains.kotlinx:kotlinx-coroutines-core:1.2.0
And is fixed in next version
org.jetbrains.kotlinx:kotlinx-coroutines-core:1.2.1
For Gradle 7.2 and later
Add in-app Gradle file
android {
packagingOptions {
resources.excludes.add("META-INF/*")
}
}
I was having the same problem and I tried this
Error: More than one file was found with OS independent path
'META-INF/proguard/androidx-annotations.pro'
Solution:
All you have to do to fix this is to add this to the android { } section in your app's 'build.gradle'
packagingOptions {
exclude 'META-INF/proguard/androidx-annotations.pro'
}
I has encountered the same error, and I found that it resulted from different modules contained the same classes from different packages.
e.g. One used androidx package, and the other used pre-androidx
I solved it by migrating the pre-androidx module to androidx using built-in feature of Android Studio: "Refactor --> Migrate to Androidx..." without excluding anything.
For your situation, you may check if you have any dependency mismatches among modules.
I have read all the answers related to getting this message in Android Studio:
More than one file was found with OS independent path
'META-INF/LICENSE'
but in this case excluding classes is no neccessary, we only need to exclude 'META-INF/DEPENDENCIES', this can be done inside the /app/build.gradle:
android{
...
...
packagingOptions {
exclude 'META-INF/DEPENDENCIES'
}
}
I my app, I was adding the jar dependencies like this:
implementation files('libs/json-simple-1.1.1.jar')
But I realised that they were already added because of the following first line in dependencies:
implementation fileTree(include: ['*.jar'], dir: 'libs')
This line adds all the jars in lib folder to app dependency.
Hence after removing the extra dependency implementation files('libs/json-simple-1.1.1.jar')
it is working fine.
Based on the answers provided by #JohnnyLambada and #Shaaban Ebrahim
For excluding nested files, I used the following.
packagingOptions {
resources.excludes.add("META-INF/**/*")
}
PS: Not spamming with same answer, but just a suggestion if you get an error something like
4 files found with path 'META-INF/gradle/incremental.annotation.processors'.
which catches errors from nested directories and FYI I had setup my dependencies using kotlin-dsl
I updated Studio from Java 7 to Java 8, and this problem occurred. Then I solved it this way:
android {
defaultConfig {
}
buildTypes {
}
packagingOptions{
exclude 'META-INF/rxjava.properties'
}
}
This work for me
packagingOptions {
exclude 'META-INF/*'
}
Adding
android.useAndroidX=true
android.enableJetifier=true
to gradle.properties worked for me.
This error is caused by adding a support library instead of AndroidX.
Make sure you use which one:
for AndroidX:
dependencies {
def multidex_version = "2.0.1"
implementation 'androidx.multidex:multidex:$multidex_version'
}
If you aren't using AndroidX:
dependencies {
implementation 'com.android.support:multidex:1.0.3'
}
Also in manifest use the application class name instead of "android.support.multidex.MultiDexApplication" in the application tag(my application class name is G):
the mistake:
<application
android:name="android.support.multidex.MultiDexApplication" >
...
</application>
right:
<application
android:name=".G" >
...
</application>
Since it's not already mentioned, you may alternatively merge the files to stay in accordance with license requirements (or just use pickFirst as stated by Daniel Reina).
packagingOptions {
merge "META-INF/LICENSE"
merge "META-INF/AL2.0"
merge "META-INF/LGPL2.1"
}
Reference: Gradle API 4.2 Packaging Options
I had a similar problem. i was getting the error message -
Error:Execution failed for task ':app:transformResourcesWithMergeJavaResForDebug'.
More than one file was found with OS independent path 'javax/annotation/WillCloseWhenClosed.java'
As stated in some of the answers above, using the below code works
'packagingOptions {
exclude 'allclasses-frame.html'
}'
But i was getting this error for 20 different files, so after excluding 20 files, i stopped and tried to find a decent solution. I had also encountered the
'Unable to execute dex: Multiple dex files' error.
I finally managed to solve this.
Firstly (as in my case WillCloseWhenClosed.java was the duplicate file), in android studio you have an option of 'search everywhere'. Write and search for the file there. There i found multiple instances of this file. So i clicked on both instances and saw their location by right clicking on the file and seeing its location when they opened in android studio.
Secondly, I figured out that i had some dependencies in gradle file. I was using the below code
dependencies {
compile 'com.google.api-client:google-api-client:1.23.0'
}
and also i had their same zip packages in the location :\Users\user\AndroidStudioProjects\git\appname\app\libs\google-http-client-1.23!.
So this was redundant and thats why gradle is finding 2 files. So i deleted my zip packages and it solved the errors for me. Be carefull while doing this. You have to figure out which is the correct file or package to be deleted.
Thirdly, gradle also makes a zip of these bug files in this location (At least for me it made) - C:\Program Files\Android\Android Studio\gradle\m2repository\com\google\code\findbugs\jsr305\1.3.9\jsr305-1.3.9.jar!
so i went and deleted the jsr305-1.3.9.jar file from here also.
If you are still confused, just go the 'search everywhere' in android studio, find instances of your file there and you would have to delete one of them. Take your time and figure out which one.
I'm having same problem and I tried this
Error:
More than one file was found with OS independent path 'META-INF/library_release.kotlin_module'
Solution:
android {
packagingOptions {
exclude 'META-INF/library_release.kotlin_module'
}
}
Worked for me. Add these to your app's build.gradle within the android{} block.
packagingOptions {
exclude 'META-INF/AL2.0'
exclude 'META-INF/LGPL2.1'
}
in gradle 7.2 and above you can fix the problem like this:
in your app/build.gradle in android block:
packagingOptions {
resources.excludes.add("META-INF/notice.txt")
resources.merges.add("META-INF/LICENSE")
resources.merges.add("META-INF/AL2.0")
resources.merges.add("META-INF/LGPL2.1")
}
put this inside the build.gradle (Module AppName)
android {
// ....
packagingOptions{
pickFirst "androidsupportmultidexversion.txt"
}
}
I faced this issue, first with some native libraries (.so files) and then with java/kotlin files. Turned out I was including a library from source as well as referencing artifactory through a transitive dependency. Check your dependency tree to see if there are any redundant entries. Use ./gradlew :app:dependencies to get the dependency tree. Replace "app" with your module name if the main module name is different.
Try to remove multidex from default config and check the build error log.
If that log is some relatable with INotification class. Use this in android{}
configurations {
all*.exclude group: 'com.android.support', module: 'support-v4'
}
This helps me.
In many of the answers on SO on this problem it has been suggested to add exclude 'META-INF/DEPENDENCIES' and some other excludes. However none of these worked for me. In my case scenario was like this:
I had added this in dependancies:
implementation 'androidx.annotation:annotation:1.1.0'
And also I had added this in gradle.properties:
android.useAndroidX=true
Both of these I had added, because I was getting build error 'cannot find symbol class Nullable' and it was suggested as solution to this on some of answers like here
However, eventually I landed up in getting error:
More than one file was found with OS independent path 'androidsupportmultidexversion.txt'
No exclude was working for me. Finally I just removed those added lines above just out of suspecion (Solved 'cannot find symbol class Nullable' in some alternative way) and finally I got rid of this "More than one file was found with OS..." build error. I wasted hours of mine. But finally got rid of it.
If you have this problem and you have a gradle .jar dependency, like this:
implementation group: 'org.mortbay.jetty', name: 'jetty', version: '6.1.26'
Interval versions until one matches and resolves the excepetion,and apply the best answer of this thread.`
If you work with multi module project and face this issue while espresso testing, you need to add packagingOptions code each gradle file. In my case , I added below code for each gradle file.
packagingOptions {
exclude 'META-INF/lib_release.kotlin_module'
}

Can you exclude classes with packagingOptions in android gradle?

I'm trying to figure out if it's possible to exclude class files or use pickfirst for classes in a jar file dependency. We always seem to run into issues where third party libs package up jars in aar files instead of using gradle dependencies and therefore cause duplicate file zip exceptions:
like this:
com.android.build.api.transform.TransformException: java.util.zip.ZipException: duplicate entry: org/apache/commons/codec/StringEncoderComparator.class
The only solution we've found so far is to unzip the aar, delete the offending jar, and rezip it back up. Is there a way to just exclude the jar or class from gradle?
Looking at the source it seems like I should be able to use packaging options. So I've tried various combinations of pick first and exclude but no luck:
packagingOptions {
pickFirst '**/StringEncoderComparator.class'
pickFirst 'org/apache/commons/codec/StringEncoderComparator.class'
pickFirst 'org/apache/commons/codec/*'
}
Use resolutionStrategy.
https://docs.gradle.org/current/dsl/org.gradle.api.artifacts.ResolutionStrategy.html
apply plugin: 'java' //so that there are some configurations
configurations.all {
resolutionStrategy {
// fail eagerly on version conflict (includes transitive dependencies)
// e.g. multiple different versions of the same dependency (group and name are equal)
failOnVersionConflict()
// prefer modules that are part of this build (multi-project or composite build) over external modules
preferProjectModules()
// force certain versions of dependencies (including transitive)
// *append new forced modules:
force 'asm:asm-all:3.3.1', 'commons-io:commons-io:1.4'
// *replace existing forced modules with new ones:
forcedModules = ['asm:asm-all:3.3.1']
// add dependency substitution rules
dependencySubstitution {
substitute module('org.gradle:api') with project(':api')
substitute project(':util') with module('org.gradle:util:3.0')
}
// cache dynamic versions for 10 minutes
cacheDynamicVersionsFor 10*60, 'seconds'
// don't cache changing modules at all
cacheChangingModulesFor 0, 'seconds'
}
}

Gradle duplicate files during packing - messages.properties of JodaTime

I replaced Java's Date classes with Joda's DateTime classes recently in my Android app. I use Jackson for parsing json. I added the following lines to my build.gradle file
compile com.fasterxml.jackson.datatype:jackson-datatype-joda:2.4.3
compile net.danlew:android.joda:2.7.1
It broke my build. The error message is duplicate files during packaging of APK. It also suggested the following option
android {
packagingOptions {
exclude 'org/joda/time/format/messages_da.properties'
}
}
There are many such files like that in JodaTime like "messages_da.properties", "messages_fr.properties". I believe those are used to provide locale based formatting.
My hunch says that these files should not be excluded. If experts out there can provide a solution for this, it would be great
This is actually an issue that results from depending on multiple joda-time modules in your project.
To fix this, you should exclude any duplicate joda-time module(s) from any dependency in your project that contains a duplicate joda-time module.
To find out what dependencies are including the duplicate joda-time, use the command ./gradlew app:dependencies to list your complete dependency graph. Then look through the list of dependencies and find the ones that includes the duplicate joda-time module. Then exclude joda-time from any dependency that includes a duplicate of it. After doing this your app will build fine.
Example of how to exclude joda-time from a dependency:
// An offending dependency that contains a duplicate joda-time.
compile('com.some.project:some-module:0.1') {
// Exclude joda-time from this dependency to remove the errors.
exclude module: 'joda-time'
}
This is the correct way to handle dependency conflicts.
I solved this issue like
android {
packagingOptions {
exclude 'org/joda/time/format/*.properties'
}
}
My dirty solution:
android {
packagingOptions {
exclude 'META-INF/maven/joda-time/joda-time/pom.properties'
exclude 'META-INF/maven/joda-time/joda-time/pom.xml'
pickFirst 'org/joda/time/format/messages.properties'
pickFirst 'org/joda/time/format/messages_cs.properties'
pickFirst 'org/joda/time/format/messages_da.properties'
pickFirst 'org/joda/time/format/messages_de.properties'
pickFirst 'org/joda/time/format/messages_en.properties'
pickFirst 'org/joda/time/format/messages_es.properties'
pickFirst 'org/joda/time/format/messages_fr.properties'
pickFirst 'org/joda/time/format/messages_it.properties'
pickFirst 'org/joda/time/format/messages_ja.properties'
pickFirst 'org/joda/time/format/messages_no.properties'
pickFirst 'org/joda/time/format/messages_nl.properties'
pickFirst 'org/joda/time/format/messages_pl.properties'
pickFirst 'org/joda/time/format/messages_pt.properties'
pickFirst 'org/joda/time/format/messages_ru.properties'
pickFirst 'org/joda/time/format/messages_tr.properties'
}
}

Categories

Resources