From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

`&gt; Task :app:mergeReleaseNativeLibs FAILED`
`UATHelper: Packaging (Android (ETC2)): FAILURE: Build failed with an exception.`
`UATHelper: Packaging (Android (ETC2)): * What went wrong:`
`UATHelper: Packaging (Android (ETC2)): Execution failed for task ':app:mergeReleaseNativeLibs'.`
`UATHelper: Packaging (Android (ETC2)): &gt; Could not resolve all files for configuration ':app:releaseRuntimeClasspath'.`
`UATHelper: Packaging (Android (ETC2)):    &gt; Could not find androidx.tonyodev.fetch2:xfetch2:3.1.6.`
`UATHelper: Packaging (Android (ETC2)):      Searched in the following locations:`
`UATHelper: Packaging (Android (ETC2)):        - <https://dl.google.com/dl/android/maven2/androidx/tonyodev/fetch2/xfetch2/3.1.6/xfetch2-3.1.6.pom>`
`UATHelper: Packaging (Android (ETC2)):        - <https://repo.maven.apache.org/maven2/androidx/tonyodev/fetch2/xfetch2/3.1.6/xfetch2-3.1.6.pom>`
`UATHelper: Packaging (Android (ETC2)):      Required by:`
`UATHelper: Packaging (Android (ETC2)):          project :app`

What is the problem in here and how can i fix this?

outdated repo link, you need to remove the `dl/` in ``<https://dl.google.com/dl/android>...`

and apparently your module is just not on Google's Maven repo (anymore?), I can't find it with a search on <https://maven.google.com/web/index.html>

instructions over there → <https://github.com/tonyofrancis/Fetch>

Have you this in your project?
```allprojects {
    repositories {
        maven { url '<https://jitpack.io>' }
    }
}```

I see gradle searches Google Maven and Maven central repositories only

There are other ways how to point gradle to an additional maven repo in setting gradle file as well

That library was only available on JCenter: <https://mvnrepository.com/artifact/androidx.tonyodev.fetch2/xfetch2/3.1.6|https://mvnrepository.com/artifact/androidx.tonyodev.fetch2/xfetch2/3.1.6> which does not exist anymore: <https://jfrog.com/blog/jcenter-sunset/|https://jfrog.com/blog/jcenter-sunset/>

It seems that library's maintainer decided that starting with 3.3.0 they are too lazy to do proper publishing and instead rely on the heavily unreliable, extremely slow, buggy, and broken by design JitPack repository solely. So you need to add the JitPack repository and change your dependency coordinates.

To mitigate the JitPack problems at least a very little bit, you should always have it as last repository in the list and with using a content repository filter to define exactly which dependencies should be taken from there.