Failed to resolve: com.ncapdevi:frag-nav:3.2.0 (jcenter sunset)

[t1d]

Dependency Resolution Issue: frag-nav

Background: On August 15, 2024, Jcenter was officially sunset, redirecting all its content to MavenCentral. However, the following dependency is not available on MavenCentral and cannot be resolved:

• classpath "de.mannodermaus.gradle.plugins:android-junit5:1.3.1.1"
• (maybe more)

Details:

1. Jcenter Sunset
   The sunsetting of Jcenter has caused issues with dependency resolution, as it now redirects to MavenCentral where some dependencies, like the one mentioned above, are not hosted.
   Official announcement: Jcenter Sunset - JFrog.
2. Jitpack.io Issues
   As a potential workaround, I explored using Jitpack.io. Unfortunately, Jitpack.io builds dependencies on-demand. This makes it unreliable for resolving the frag-nav dependency because of the mentioned jcenter redirect.
   Reference: Jitpack Building. Failed to resolve: com.ncapdevi:frag-nav:3.2.0 jcenter error #252 and @eggplants comment in this issue.
3. Gradle Caching Masking the Issue
   The issue was initially discovered during the setup of a new development environment. The problem did not manifest for my co-workers due to Gradle's caching mechanism, which retained the dependency locally. Even after invalidating caches in Android Studio, the issue persists on a fresh setup because the required dependency is no longer resolvable.

Proposed Next Steps

I'm open to working on resolving this issue, but the repository appears to have been inactive for a few years. Given this, I’m wondering whether you, @ncapdevi, or other maintainers would suggest a long-term solution or have any input on the best course of action.

I wanna made this insights available for everyone because as seen in the repository there are still people using frag-nav

Any guidance or suggestions would be appreciated!

[ncapdevi]

Hi @t1d yes, if I can get some feedback that the library is still in active use, then taking a weekend to migrate things over seems like the right call, and something that I could do.

[GerardBizagi]

Hi @ncapdevi, we have the same problem and we continue using the library in version 2.4.0, we hope to continue using it, thank you.

[bryancubillos]

Its impossible build the pipeline in Azure with this, we use 2.4.0 version and don't works

[headsmanxxx]

Hi @ncapdevi, we have the same issue and we need this library in any way. Thank you!

Failed to transform FragNav-3.3.0.aar (com.github.ncapdevi:FragNav:3.3.0) to match attributes {artifactType=android-databinding, org.gradle.category=library, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-api}.
> Could not find FragNav-3.3.0.jar (com.github.ncapdevi:FragNav:3.3.0).
Searched in the following locations:
https://jitpack.io/com/github/ncapdevi/FragNav/3.3.0/FragNav-3.3.0.aar
https://jitpack.io/com/github/ncapdevi/FragNav/3.3.0/FragNav-3.3.0.jar

[PaulineKlein]

Hi @ncapdevi, we have the same issue when building with Github actions. We got the same error as @headsmanxxx (we are also using version 3.3.0)
Thank you 🙏

[amatsegor]

Hi @ncapdevi , can confirm it is in use (3.3.0), I would be extremely grateful if you'd migrate it. Thank you!

[thorre]

Hi @ncapdevi we have the same issue and our release pipeline is now down :-(
We use version 3.3.0

[eggplants]

FragNav build is failing.
https://jitpack.io/com/github/ncapdevi/FragNav/3.3.0/build.log

android-junit5 has to be updated to 1.7.1.0 or higher.

FragNav/build.gradle

Line 12 in 498317c

classpath "de.mannodermaus.gradle.plugins:android-junit5:1.3.1.1"

https://jcenter.bintray.com/de/mannodermaus/gradle/plugins/android-junit5/
↓ redirect
https://repo1.maven.org/maven2/de/mannodermaus/gradle/plugins/android-junit5/

[t1d]

Hi All, thanks for those replies. So I'm seeing this Issue getting a lot of traction, which confirms, that the lib is still in use.
So I'm investing a few hours and see if i can fix the problem.

[Enjot]

This Udemy course uses this library and for now it's impossible to build a GitHub project that is linked to this course so students can't do exercises that are included there.

[abhishekgupta-mset]

Hi @ncapdevi we have the same issue and our release pipeline is now down :-(
We use version 3.3.0

[mohammadhaseeb-mset]

Hi @ncapdevi we are also facing the same issue causing our release pipeline resulting in failure.
We are using version 3.3.0

[muhammadsabeelahmed-mset]

Hii @ncapdevi we are also facing same issue, our pipeline is down now.. using 3.3.0.

[eggplants]

@abhishekgupta-mset @mohammadhaseeb-mset @muhammadsabeelahmed-mset You can fork and modify this repo under Apache License freely.

[davit-zakaryan]

Hey, the same issue here. Who can help with this? I am already thinking about forking the lib and put it into the project!!

[TonyLead]

also have problem

[TonyLead]

maybe author can share aar ?

[A7ak]

@ncapdevi I have added aar and jar file for 3.3.0
PR link

[sunenielsen]

@A7ak do you also have one for 2.4.0, as my project has not been upgraded to use version 3?

[t1d]

@ncapdevi I managed to make the frag-nav project running but i have issues with the demo project. I invested a few hours but did not manage to made it work. I could push the changes to a branch.

[t1d]

@t1d

I could push the changes to a branch

This one? https://github.com/t1d/frag-nav-reworked

Sorry haven't pushed it yet. There you go:
https://github.com/t1d/FragNav/tree/misc/dump-dependencies

[A7ak]

use this fix
https://medium.com/@ag7aka/how-to-find-and-integrate-a-library-from-cache-in-android-jcenter-shudown-63682c8535f6

[A7ak]

@A7ak do you also have one for 2.4.0, as my project has not been upgraded to use version 3?
#255 (comment)

[bryancubillos]

Any update?

[voghDev]

Hi! thanks for the active work in this library!
We're still using version 3.3.0 in our App. 1M+ downloads 🙂
It'd be awesome to have an available dependency. For the moment we'll use the jar and the aar

[voghDev]

This is the final dependency we've used after some failed attempts with other combinations:

root build.gradle:

allprojects {
  repositories {
    google()
    mavenCentral()
   ...
    maven(url = "https://jitpack.io") // <-- Make sure you have this dependency added
  }
}

app/build.gradle

implementation "com.github.ncapdevi:fragnav:3.3.0"

it is currently working for us. I hope it does for you too

[jordizspmobile]

Solved! Add the next code in settings.gradle:

import org.gradle.api.initialization.resolve.RepositoriesMode


dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
        maven { url "https://maven.google.com" }
        maven { url "https://jitpack.io" }
    }
}

Remove from root build.gradle:

allprojects {
   // Remove repositories from here
    repositories { -> Removed
        google()
        mavenCentral()
        maven { url "https://maven.google.com" }
        maven { url "https://jitpack.io" }
    }
   ....

Use your dependency like:

implementation "com.github.ncapdevi:fragnav:3.3.0"