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
Bug Description
Not all build dependencies can be resolved during a build on a freshly checked out BEAM Android-Wallet. This is because there are dependencies on JFrog referenced and JFrog Bintray / JCenter was sunset in August of 2024. It appears to be up because requests are now re-directed to Maven Central, but Maven Central was not synchronized with JFrog's repository beforehand. Maven Central's stricter administrative requirements mean that it is not likely that lots of outdated packages and their dependencies will ever make it onto Maven Central.
To Reproduce
Steps to reproduce the behavior:
Build using Gradle
Expected Behavior
Android-Wallet should build via all dependencies being resolved
Problem Output
Could not determine the dependencies of task ':app:compileBeamtestnetDebugJavaWithJavac'.
> Could not resolve all task dependencies for configuration ':app:beamtestnetDebugCompileClasspath'.
> Could not find org.jetbrains.anko:anko-commons:0.10.4.
Required by:
project :app
> Could not find androidx.tonyodev.fetch2:xfetch2:3.1.4.
Required by:
project :app
> Could not find com.samigehi:loadingview:1.1.
Required by:
project :app
> Could not find me.relex:circleindicator:2.1.4.
Required by:
project :app
> Could not find jp.wasabeef:blurry:3.0.0.
Required by:
project :app
> Could not find com.mikhaellopez:gradientview:1.1.0.
Required by:
project :app
Possible Solution
We build all of the packages (from Github, mainly) ourselves
Over the past month or so, I have been doing this
Some of the packages involved have dependencies that were only available on JFrog as well
A few Github repositories have no tags or versioning information
There have definitely been version conflicts (usually incorrect method prototypes discovered) that can only be resolved by checking out the right commit, unassociated with a specific tag/brach
Thus, the risk to users with manually building dependencies
Others can upload their cached dependencies into the repository
Obviously, this is a temporary fix. Many of these packages are quite out of date and alternatives must be implemented.
Setup
OS: Ubuntu Linux (direct gradlew invocation) as well as OSX (Android Studio)
The text was updated successfully, but these errors were encountered:
Bug Description
Not all build dependencies can be resolved during a build on a freshly checked out BEAM Android-Wallet. This is because there are dependencies on JFrog referenced and JFrog Bintray / JCenter was sunset in August of 2024. It appears to be up because requests are now re-directed to Maven Central, but Maven Central was not synchronized with JFrog's repository beforehand. Maven Central's stricter administrative requirements mean that it is not likely that lots of outdated packages and their dependencies will ever make it onto Maven Central.
To Reproduce
Steps to reproduce the behavior:
Expected Behavior
Android-Wallet should build via all dependencies being resolved
Problem Output
Possible Solution
Setup
OS: Ubuntu Linux (direct
gradlew
invocation) as well as OSX (Android Studio)The text was updated successfully, but these errors were encountered: