React Native Android Duplicate file error when generating apk

Question

When I am trying to generate android apk by using ./gradlew installRelease, I get this error in console:

~/React-Native/mockingbird/android/app/build/intermediates/res/merged/release/drawable-mdpi-v4/src_resources_img_loading.gif: error: Duplicate file.
~/React-Native/mockingbird/android/app/build/intermediates/res/merged/release/drawable-mdpi/src_resources_img_loading.gif: Original is here. The version qualifier may be implied.

I tried Build->Clean Project via Android Studio and ran ./gradlew installRelease again; it didn't work either.

Also, I tried deleting the build folder, but it doesn't help either.

That's a really weird thing i've faced too. One of the quick solutions is to remove drawable resources completely (or just move somewhere outside the project directory) and rebuild the project. — Aleksandr Medvedev
– Aleksandr Medvedev, Commented Nov 2, 2017 at 21:19
@AleksandrMedvedev Thanks for your answer, but it doesn't work here 😢 — Shongsu
– Shongsu, Commented Nov 2, 2017 at 21:40
please check my answer to a duplicate question: stackoverflow.com/a/54066718/427622 — Fareed Alnamrouti
– Fareed Alnamrouti, Commented Jan 6, 2019 at 23:10

Nhan Cao · Accepted Answer · 2019-02-25 19:51:48Z

147

Give some tips for you, hope it's work.

Update with "react": "16.7.0", "react-native": "0.57.8"

Custom node_modules/react-native/react.gradle to solve the Duplicate file error perfectly. Add following code into currentBundleTask's creation block (after doFirst block)

doLast {
    def moveFunc = { resSuffix ->
        File originalDir = file("${resourcesDir}/drawable-${resSuffix}");
        if (originalDir.exists()) {
            File destDir = file("$buildDir/../src/main/res/drawable-${resSuffix}");
            ant.move(file: originalDir, tofile: destDir);
        }
    }
    moveFunc.curry("ldpi").call()
    moveFunc.curry("mdpi").call()
    moveFunc.curry("hdpi").call()
    moveFunc.curry("xhdpi").call()
    moveFunc.curry("xxhdpi").call()
    moveFunc.curry("xxxhdpi").call()
}

You can create script to do it automatically.

Create android-react-gradle-fix file
Create script android-release-gradle-fix.js file
Update package.json file:

"scripts": { "postinstall": "node ./android-release-gradle-fix.js" },

That's it! Run npm install to get awesome.

Note: If you run npm install on ci like jenkins, you may get error: postinstall: cannot run in wd %s %s (wd=%s) node => just use npm install --unsafe-perm instead

edited Feb 25, 2019 at 19:51

answered Nov 3, 2017 at 11:15

Nhan Cao

2,5051 gold badge19 silver badges13 bronze badges

Sign up to request clarification or add additional context in comments.

13 Comments

George Miranda Over a year ago

This solution worked for me, but my question is how does this error happen in the first place since it only happens on my side branch that I share with another developer?

akaMahesh Over a year ago

Thank you so much..you saved my ass. Although i have a question, do i need to insert this code everytime after running npm install, Is it a good idea to modify gradle from node_modules? i seriously doubt it

ThaJay Over a year ago

This is in react-native now (I'm on version 0.56.0) but I still have this error. I'm starting to go crazy, this is blocking me for way too long now.

Apperside Over a year ago

This solution does not work if you are using react native >=0.57, @Cawfree 's solution does

Sumi Straessle Over a year ago

this didn't work for me, removing files in drawable did.

|

Jatin Bhuva · Accepted Answer · 2023-01-19 11:43:58Z

At the time of writing, the more recent versions of React Native (>0.57.0) have increased the Gradle wrapper level to 4.4 and the Gradle plugin to 3.1.4, as indicated by the changelog. This has the effect of making the Gradle build process store the results of AAPT, which are now required, within a different directory than previously.

In terms of Nhan Cao's awesome workaround, we need to make a slight modification to prevent duplicate resource collisions, since it looks to be pointed at the old directory and not the app's generated directory. By changing the target directory where these duplicate files are merged together after the resources have been generated, we can still dedup the resources.

The existing react.gradle refers to the path below:

$buildDir === <project-working-directory>/android/app/build

The duplicate file paths can appear between:

file("$buildDir/../src/main/res/drawable-${resSuffix}")
file("$buildDir/generated/res/react/release/drawable-${resSuffix}")

As a workaround, we can update Nhan's solution as follows (be sure to include this within the currentBundleTask after the declaration of doFirst in react.gradle:

doLast {
    def moveFunc = { resSuffix ->
        File originalDir = file("$buildDir/generated/res/react/release/drawable-${resSuffix}");
        if (originalDir.exists()) {
            File destDir = file("$buildDir/../src/main/res/drawable-${resSuffix}");
            ant.move(file: originalDir, tofile: destDir);
        }
    }
    moveFunc.curry("ldpi").call()
    moveFunc.curry("mdpi").call()
    moveFunc.curry("hdpi").call()
    moveFunc.curry("xhdpi").call()
    moveFunc.curry("xxhdpi").call()
    moveFunc.curry("xxxhdpi").call()
}

If your app depends on /raw assets too, the method outlined below should help you:

doLast {
    def moveFunc = { resSuffix ->
        File originalDir = file("$buildDir/generated/res/react/release/${resSuffix}");
        if (originalDir.exists()) {
            File destDir = file("$buildDir/../src/main/res/${resSuffix}");
            ant.move(file: originalDir, tofile: destDir);
        }
     }
     moveFunc.curry("drawable-ldpi").call()
     moveFunc.curry("drawable-mdpi").call()
     moveFunc.curry("drawable-hdpi").call()
     moveFunc.curry("drawable-xhdpi").call()
     moveFunc.curry("drawable-xxhdpi").call()
     moveFunc.curry("drawable-xxxhdpi").call()
     moveFunc.curry("raw").call()
}

If your app also uses a custom "build types" other than release, such as preRelease or stagingRelease(Android Gradle Plugin allows you to define them in build.gradle), you should change originalDir variable like below:

# from
File originalDir = file("$buildDir/generated/res/react/release/drawable-${resSuffix}");
# to 
File originalDir = file("$buildDir/generated/res/react/${targetName}/drawable-${resSuffix}");

For anyone who build an apk with productFlavors the originalDir in this answer should update accordingly; for example mine would be "$buildDir/generated/res/react/develop/release/drawable-${resSuffix}"
wow, thank you for saving my day, that's really helpful and appreciative

Flow Wolf · Accepted Answer · 2018-06-15 13:36:51Z

37

Remove the files you might have on:

android/app/src/main/res/drawable-mdpi/
android/app/src/main/res/drawable-xhdpi/
android/app/src/main/res/drawable-xxhdpi/

Run Build again, This fixed the issue for me.

answered Jun 15, 2018 at 13:36

Flow Wolf

5194 silver badges5 bronze badges

5 Comments

ThaJay Over a year ago

I cleaned out the whole res/ folder and backed it up. Then I only added mipmap/ic_launcher.png and values/ with strings.xml and styles.xml. Now it finally works after the most frustrating day and a half this year.

Mandar Belkunde Over a year ago

its works perfect for me... i am resolving from last one day.. thnx a lot

laurent Over a year ago

Thanks, that fixed it for me. I normally only build from the command line, and when opening the project in Android Studio I didn't notice it created these directories and thus duplicate resources.

matt Over a year ago

"Android resource linking failed" :/

123dev123 Over a year ago

For me works - remove folder android/app/src/main/res/raw

Joshua Pinter · Accepted Answer · 2019-03-19 21:15:23Z

20

Do not run `react-native bundle` prior to `./gradlew assembleRelease`.

For myself, I was running react-native bundle prior to running ./gradlew assembleRelease.

I was getting a similar duplicate error message with one of my assets.

Looking at the ./gradlew assembleRelease output, I could tell that it builds the JS bundle by itself (thanks to apply from: "../node_modules/react-native/react.gradle" in your build.gradle file) so it was not necessary to manually run react-native bundle before hand.

If I simply did not run react-native bundle before running ./gradlew assembleRelease everything worked great.

I tested the Release APK and the JS bundle loads fine, including all images.

My only concern is whether the source maps --sourcemap-output (for Bugsnag) will be created. If not, I'm sure there's a way to have ./gradlew assembleRelease generate those as well. I just have not tested it yet.

edited Mar 19, 2019 at 21:15

answered Mar 31, 2018 at 15:50

Joshua Pinter

48k23 gold badges262 silver badges258 bronze badges

4 Comments

zszep Over a year ago

Didn't work for me. The accepted answer solved it for me, but had to also put android.enableAapt2=false into the gradle.properties file.

Joshua Pinter Over a year ago

Coming back to my own answer here. This used to fix it but even after remove the bundle prior to assembleRelease, it's not longer working on React Native 0.57.8.

Joshua Pinter Over a year ago

Hmm, coming back here and it's still the correct answer for me. The only duplicate resource errors I was getting were related to react-navigation. We were on an old version, 2.3.1, and after upgrading to 2.18.3 the error went away. But, bundling the react-native JS before running ./gradlew assembleRelease still caused the error.

Hugo Gresse Over a year ago

coming back now, you never need to manually bundle the js, assembleRelease will do it for you, so you are right. (also, you can delete the index.android.bundle, no need for that, only if building via Android Studio)

WadeStar · Accepted Answer · 2018-12-27 16:41:55Z

In order to get my build working for React Native 0.57.5, I used Mapsy's answer with a minor enhancement. I needed to be able to build for multiple flavors and generally I try to avoid hardcoding things. When looking through my react.gradle file, I found it had the following variable defined:

def resourcesDir = file("$buildDir/generated/res/react/${targetPath}")

So instead of hardcoding the build type/flavor in the path like this:

File originalDir = file("$buildDir/generated/res/react/release/drawable-${resSuffix}");

I instead used the resourcesDir variable to set the originalDir path like this:

File originalDir = file("${resourcesDir}/drawable-${resSuffix}");

As a result, my doLast looks like this:

doLast {
            def moveFunc = { resSuffix ->
                File originalDir = file("${resourcesDir}/drawable-${resSuffix}");
                if (originalDir.exists()) {
                    File destDir = file("$buildDir/../src/main/res/drawable-${resSuffix}");
                    ant.move(file: originalDir, tofile: destDir);
                }
            }
            moveFunc.curry("ldpi").call()
            moveFunc.curry("mdpi").call()
            moveFunc.curry("hdpi").call()
            moveFunc.curry("xhdpi").call()
            moveFunc.curry("xxhdpi").call()
            moveFunc.curry("xxxhdpi").call()
        }

suther · Accepted Answer · 2018-08-10 14:31:46Z

5

For me it work to remove the folder: android/build and run ./gradlew assembleRelease again.

answered Aug 10, 2018 at 14:31

suther

13.8k6 gold badges73 silver badges105 bronze badges

Comments

Esben von Buchwald · Accepted Answer · 2019-08-13 20:39:03Z

4

What worked for me was simply adding this extra command in package.json, and use that for building:

    "android-build-release": "cd ./android && rm -rf app/src/main/res/drawable* && ./gradlew app:assembleRelease",

answered Aug 13, 2019 at 20:39

Esben von Buchwald

3,1392 gold badges39 silver badges48 bronze badges

1 Comment

Blue Bot Over a year ago

worked like a charm, on 0.56.0 and up, the selected solution (updating react.gradle) is not working. This one really should be selected as the right one

Alen.Toma · Accepted Answer · 2021-01-31 05:00:49Z

2

1.Delete drawable-xxx folders 2.Delete raw inside src -> main -> res folder then

3.run this command in terminal:

react-native bundle --dev false --platform android --entry-file index.js --bundle-output ./android/app/src/main/assets/index.android.bundle --assets-dest ./android/app/src/main/res_temp

4.then generate signed apk using keystore, alias and passwords using terminal or android studio

edited Jan 31, 2021 at 5:00

Alen.Toma

4,8782 gold badges19 silver badges37 bronze badges

answered Dec 7, 2020 at 11:52

Andriya

2412 silver badges15 bronze badges

Comments

Richard Lovell · Accepted Answer · 2019-01-09 03:20:33Z

A way to remove the error would be to:

put your images in the android/app/src/main/res/drawable folder (create a “drawable” folder if one doesn’t exist)
delete all the drawable folders that have suffixes (i.e. drawable-hdpi, drawable-mdpi, etc)
don’t bundle assets (i.e. don’t run: react-native bundle …)
run Gradle’s assembleRelease

However, this is not an ideal solution because each image will only have one resolution for all device sizes. For images that are too big for a device it leaves downscaling to the device and leads to download size and speed issues, and for images too small for a device it leads to diminished image quality.

One convenient solution I’ve found is to use an Android Studio plugin called Android Drawable Importer. To use it after it is installed:

open your project in Android studio and navigate to: android/app/src/main/res/drawable
right click on the folder and choose: New > Batch Drawable Import
select and configure image assets to import

The plugin will handle the generation of the drawable folders and correct image sizes. Once you’ve imported your image, you should be able to run Gradle’s assembleRelease without the duplicate resources error.

Peter Couture · Accepted Answer · 2023-04-02 13:43:41Z

0

If anyone else is running into this and the doLast solution isn't working it's because you do not have to run react-native bundle anymore before you run bundleRelease. This took hours of head banging because of how many posts out there I found saying doLast solves it.

answered Apr 2, 2023 at 13:43

Peter Couture

216 bronze badges

Comments

King Oni-Gbarago · Accepted Answer · 2024-03-02 18:59:06Z

0

based on @Esben von Buchwald 's answer, i added to the script to delete raw folder also.

"android-build-release": "cd ./android && rm -rf app/src/main/res/drawable* && rm -rf app/src/main/res/raw && ./gradlew app:assembleRelease",

Hope it works for you

answered Mar 2, 2024 at 18:59

King Oni-Gbarago

35 bronze badges

Collectives™ on Stack Overflow

React Native Android Duplicate file error when generating apk

11 Answers 11

13 Comments

2 Comments

5 Comments

Do not run `react-native bundle` prior to `./gradlew assembleRelease`.

4 Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

11 Answers 11

13 Comments

2 Comments

5 Comments

Do not run react-native bundle prior to ./gradlew assembleRelease.

4 Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related

Do not run `react-native bundle` prior to `./gradlew assembleRelease`.