-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node: sync issues #647
Comments
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.
|
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. |
@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) |
@freQniK Not sure what you mean with output, but the UI doesn't show any errors it just doesn't load. |
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. |
No description provided.
The text was updated successfully, but these errors were encountered: