Node: sync issues

[Maxnflaxl]

No description provided.

[NeutrinoResonance]

Currently having issues with package resolution both when using Android Studio as well as well as Gradle directly.

Some research on these makes it appear that many of these packages are simply not available because of JCenter being shut down. MavenCentral and other repositories simply do not have them.

The Github repositories, however, often are. Packages could be imported or sub-module'd into this repository.

Course of action consensus is needed.

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:
 - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

[freQniK]

JCenter is not shut-down. IT was made readonly in early 2021 and you can still use it. In fact, I used it to build the recent APK of Cosmostation back in December (A popular Cosmos wallet). (https://github.com/MathNodes/cosmostation-android/releases/tag/v1.10.20)

Gradle will produce a warning and it is deprecated but that doesn't mean you cannot use it.

[freQniK]

@Maxnflaxl Do we have any output of syncing errors? I've never run into this and I have BEAM Android on 3 different Androids (Pixel 4, Pixel 5 and Pixel 6 - All Graphene)

[Maxnflaxl]

@freQniK Not sure what you mean with output, but the UI doesn't show any errors it just doesn't load.
Good to know that it works on the Pixels.

[freQniK]

I just tried again on my Pix Six and the mobile node had no problems syncing. What I mean is debug output from a log of sorts. To better identify the source of the error.

Also, if we have Android versions where this isn't working and possibly make/model of phone it would help immensely with vm phones in studio.

[NeutrinoResonance]

Recall that the error I'm running into is a pre-requisite to fixing any issue, not just the one @Maxnflaxl pointed out.

JFrog Bintray / JCenter was sunset in August of 2024 requests are now re-directed to Maven Central, which was not synchronized with JFrog's repository before hand. Therefore, JCenter appears up but it is not and 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.

The only way to fix this is to, temporarily, have a copy of these packages.

Over the past month or so, I have been building these outdated, orphaned packages. However, it is an ugly process that has involved guessing which commits will work for building the software. I do not like putting BEAM users at risk should a bug arise due to an incorrect build arising from a guess-work laden build process.

For that reason, I am asking those who are currently able to build Android-Wallet to upload their cache of the relevant dependencies. Although this is not ideal, it eliminates a potentially massive source of guesswork-induced build error.

[NeutrinoResonance]

Refer to #648