You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Caused by: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find any version that matches com.twofortyfouram:android-annotation:[1.0.2,3.0).
Versions that do not match: 3.0.0
Searched in the following locations:
- https://jcenter.bintray.com/com/twofortyfouram/android-annotation/maven-metadata.xml
- https://dl.google.com/dl/android/maven2/com/twofortyfouram/android-annotation/maven-metadata.xml
Required by:
project :app > com.twofortyfouram:android-plugin-client-sdk-for-locale:4.0.3
project :app > com.twofortyfouram:android-plugin-client-sdk-for-locale:4.0.3 > com.twofortyfouram:android-spackle:2.0.3
I suppose manually downloading and putting it as a local dependency might work with either the archived version or the new one. And just continually manually doing that. (There is a problem with this so a more complex way would be necessary.)
Remove it from the project. (This is the best way to go imo. Tasker should still be able to open the app on boot btw without it so its more for the other things.)
Maybe the developer of it has something else available? Although I'm having trouble finding what it is if that exists. (What I do find (see below) looks like a pain and I won't do it. Not for this.)
Maybe forking it and adding to maven yourself. (I just wouldn't.)
Might be a way to get the jcenter redirect working or that which is on maven. (Can't see if this is a good idea or if it will even work here as I couldn't get it to work in the time I spent.)
Maybe waiting for android-monorepo to be better in implementation.
I think this is what the developer currently has...
Looks like android-plugin-client-sdk-for-locale is archived for android-monorepo...
android-monorepo, the git readme suggests it isn't available publicly and needs a git account to access and goes on suggesting to put those account details into the project. For that, one would hope that it gets removed during sync to git and carries some amount of risk... should the removal during sync ever fail. Not the best idea anyone has ever had - from what I know tokens uploded to git projects has historically been a bad issue. Its a bad security risk.
I've removed it from my build. Its not expected that I will deal with this further. You may have to deal with it yourself. Sorry :\
Pull request created so you can decide on that one and its there #250 :) Will leave this open for now.
The text was updated successfully, but these errors were encountered:
Xavron
changed the title
twofortyfouram is causing build problems lately
twofortyfouram as of now causes build failure
Aug 21, 2024
Xavron
changed the title
twofortyfouram as of now causes build failure
twofortyfouram as of now causes build failure from jcenter end of life
Aug 22, 2024
Problem
Reason for that problem
Looks like it from https://jcenter.bintray.com being fully end of life on the 15th and cannot even use it to read for project building as of now. It redirects to maven but that isn't working for this for whatever reason. https://jfrog.com/blog/jcenter-sunset/
Possible fix
I suppose manually downloading and putting it as a local dependency might work with either the archived version or the new one. And just continually manually doing that. (There is a problem with this so a more complex way would be necessary.)
Remove it from the project. (This is the best way to go imo. Tasker should still be able to open the app on boot btw without it so its more for the other things.)
Maybe the developer of it has something else available? Although I'm having trouble finding what it is if that exists. (What I do find (see below) looks like a pain and I won't do it. Not for this.)
Maybe forking it and adding to maven yourself. (I just wouldn't.)
Might be a way to get the jcenter redirect working or that which is on maven. (Can't see if this is a good idea or if it will even work here as I couldn't get it to work in the time I spent.)
Maybe waiting for android-monorepo to be better in implementation.
I think this is what the developer currently has...
Looks like android-plugin-client-sdk-for-locale is archived for android-monorepo...
android-monorepo, the git readme suggests it isn't available publicly and needs a git account to access and goes on suggesting to put those account details into the project. For that, one would hope that it gets removed during sync to git and carries some amount of risk... should the removal during sync ever fail. Not the best idea anyone has ever had - from what I know tokens uploded to git projects has historically been a bad issue. Its a bad security risk.
I've removed it from my build. Its not expected that I will deal with this further. You may have to deal with it yourself. Sorry :\
Pull request created so you can decide on that one and its there #250 :) Will leave this open for now.
The text was updated successfully, but these errors were encountered: