Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1)

Question

I have a unity project I am exporting that project as android studio project while opening the android studio project I am getting this error

Gradle sync failed: Could not find manifest-merger.jar
    (com.android.tools.build:manifest-merger:26.0.1).
    Searched in the following locations:
    https://jcenter.bintray.com/com/android/tools/build/manifest-merger/26.0.1/manifest-merger-26.0.1.jar

I have a few old exported project that was working fine before but today they are also giving the same error.

check if you have two activities with same name in the manifest — sourabh kaushik, Jan 14 '19 at 13:20
does that have intent filter "android.intent.action.MAIN" and "android.intent.category.LAUNCHER" ?? — sourabh kaushik, Jan 14 '19 at 13:25

score 54 · Accepted Answer · edited Jul 14 '19 at 09:41

I finally fixed the issue. This may be a workaround but it works. So if anyone having this issue, just follow this:

Swap the position of jcenter() and google() in project gradle file and in also all the other module you have in your project. Like in mine I have crashlytics, fabric so just remember to make the changes in their build.gradle file as well:
```
buildscript {
    repositories {
        jcenter()
        google()
    }
}
```
to
```
buildscript {
    repositories {
        google()
        jcenter()
    }
}
```
Before building your project again go to your project folder and delete the .gradle folder from your project and then build your project.

score 16 · Answer 2 · answered Mar 01 '19 at 03:00

16

Go to Publishing Settings/Build, enable Custom Gradle Template
Go to Assets/Plugins/Android/mainTemplate.gradle and change the postion from

  buildscript {
    repositories {
        jcenter()
        google()
}

to


 buildscript {
   repositories {
      google()
      jcenter()
}

Remove gradle cache and rebuild. For Mac you can run rm -rf $HOME/.gradle/caches/ in terminal.

answered Mar 01 '19 at 03:00

Vincent Plus

250
1
7

thanks! saved my day. it worked after removing cache, rm -rf $HOME/.gradle/caches/ – Deepak sharma Feb 20 '20 at 09:50
Thanks for letting me know. So happy to hear that. @Deepaksharma – Vincent Plus Feb 21 '20 at 03:15

score 0 · Answer 3 · answered Jan 14 '19 at 20:15

0

Jcenter no longer hosts google dependencies, these can be resolved from "https://maven.google.com" so you can simply add that to the resolvers list along with jcenter.

Regards, Itamar

answered Jan 14 '19 at 20:15

Itamarb

111
3

you mean adding maven { url 'https://maven.google.com' } this into repositories right? – Ayush Malviya Jan 15 '19 at 06:03

score 0 · Answer 4 · answered Feb 06 '19 at 05:47

The problem is definitely having jcenter() above google(). However for me, my build.gradle was correct. The problem happened because of one of my dependencies library had that problem. The problem seemingly started happening out of nowhere, probably because my jar was cached.

I solved the problem by upgrading my problematic library to latest version as that contained a fix.

Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.0.1)

4 Answers4