migrating to mavenCentral from jcenter - android-studio

Android studio gave me a couple of warnings that I need to migrate away from jcenter(). I am new to android developing so started looking online for replacements. I found an article that said that I should move to MavenCentral. I don't know if this is a good replacement. What do you guys think?
I tried to build my project with jcenter() replaced by mavenCentral() but it won't build because I need:
implementation 'com.synnapps:carouselview:0.1.5'
Does anyone know a solution?

switch back to jcenter and keep using jcenter for the time being and if possible try to find replacement for that if its not appearing in other repo. That's what I've been doing

Related

GradleException: Crashlytics could not determine stripped/unstripped native library directories

There is plenty of "chatter", but I did not find an answer for my project.
While performing the Gradle Sync in my project with Crashlytics, Gradle fails to sync. I have other projects that are just fine and when I 'diff' the build.gradle files and other Android Studio settings, they have the same values and settings related to Crashlytics.
A problem occurred configuring project ':app'.
> org.gradle.api.GradleException: Crashlytics could not determine stripped/unstripped native library directories for project ':app', variant Debug. These are required for generating symbol files when NDK build tasks cannot be automatically inferred. Please specify strippedNativeLibsDir and unstrippedNativeLibsDir in the firebaseCrashlytics extension.
I am not looking for someone to triage my configuration, instead I want to know where in my project files can I find the "firebaseCrashlytics extension" and its configuration and where are the stripped and unstripped files so I can supply a path? If you know the answer from documentation, please share the link.
Make sure your android/app/build.gradle has the following:
release {
// ...
firebaseCrashlytics {
nativeSymbolUploadEnabled true
strippedNativeLibsDir 'build/intermediates/stripped_native_libs/release/out/lib'
unstrippedNativeLibsDir 'build/intermediates/merged_native_libs/release/out/lib'
}
// ...
}
See https://github.com/invertase/react-native-firebase/issues/4253#issuecomment-797187492
In my case, I had a few projects cloned locally of the same repo. One of them was for a too old branch. Like 3-4 years back. For it, I have given a path to another NDK in the local.properties file.
ndk.dir=C\:\\NDK\\android-ndk-r13b\\android-ndk-r13b
It was causing my problem with the recent branches. After deleting it - it worked. So even if it is not the exact same case for you - it is most likely that you are building with the wrong SDК. Try updating in the SDK manager or maybe actually try explicitly saying what you need as I was doing above.
In my project-level build.gradle, Android Studio recommends updating the the firebase-crashlytics-gradle from 2.1.1 to 2.4.1. When I take the upgrade recommendation, the gradle sync fails, therefore I am unable to build my project. The error was obscured as I inherited this old project that is several versions behind and I updated all (most) of the frameworks and could not pin-point to this single dependency. I started over and upgraded selectively piecemeal until this was the lone down-level dependency.
I will try again at a later time when there is yet another update
to include.
dependencies {
classpath 'com.android.tools.build:gradle:4.1.2'
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
classpath 'com.google.gms:google-services:4.3.5'
classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
classpath 'org.jacoco:org.jacoco.core:0.8.0'
// Unable to build with v2.4.1 of firebase-crashlytics-gradle on this version of build (2021/02/02)
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.1.1'
}

No cached version of org.jetbrains.kotlin:kotlin-gradle-plugin:1.4.10 available for offline mode

I am using android studio 4.0 and whenever i create a new project offline(without access to internet) it gives me this error and I haven't access to internet most of times. I tried toggling offline mode button and everything but again I need to have access to internet for complete build. Is there any solution to this or you need to have access to internet when build you project?
I used to use Java for android app development and could build project offline too. but I have migrated to Kotlin and this give me this error. Please, answer!!
I tried this. I disabled offline mode. You might get this error "Unknown host 'jcenter.bintray.com'" when you build. To handle this error, try the below steps.
Go to project >> build.gradle. Add the below into your projects.
android{ allprojects {
repositories { google()
jcenter()
maven {url"https://jitpack.io"} }}

libGDX, project build fail. Could not detemine java version '9.0.1'

I am new to libGDX, just planning to create a new project. but the generation of project fail with this error displayed
"Could not detemine java version '9.0.1'.
I have linked the SDK path like how I linked it in android studio. need help. I found it might be something to do with the gradle version. do you guys know how to let libGDX uses the latest gradle?
Check this issue, already in libgdx issue tracker.
According to this discussion, Gradle update may solve this issue so wait for this issue to be resolved.

Dependencies search result ended up in no result but when hardcored; it worked. Why?

I tried to add jackson dependancies in android studio, the dependencies search within the android studio returned some other libraries, but when i hardcored these dependencies it synced successfully. So basically the results came from rather than bintray.com ?
compile 'com.fasterxml.jackson.core:jackson-databind:2.8.5'
compile 'com.fasterxml.jackson.core:jackson-core:2.8.5'
compile 'com.fasterxml.jackson.core:jackson-annotations:2.8.5'
It seems that all the dependencies exist in JCenter (under bintray.com).
Here are the links in Jcenter to each of the dependencies you were looking for:
jackson-databind
jackson-core
jackson-annotations
You can also see that the JCenter is updated until version 2.8.6.
Please check if your Android Studio is configured to get all its dependencies from JCenter.
I assume that maybe there is a mistake in the basic search you have made, so if you can provide us with more information it will be much more helpful.
In any case you can contact JFrog Support to get more helpful details.
I am with JFrog, the company behind bintray and artifactory.

Converting android ndk build files to gradle

Is there any documentation on converting a application.mk/android.mk file to a gradle based build.gradle file?
good links, QArea. Thanks a lot!
At this moment NDK support in Gradle are very limited. If you need to assemble something that gradle not provides that function
I do like this.
I collect the old-fashioned, but to .so-patches automatically picks up the Gradle-plugin:
ndk-build -j4 NDK_LIBS_OUT=src/main/jniLibs
Otherwise, you must wait for next version of gradle 0.13. Devs promise that NDK will fix integration with NDK.
I made a script tool to convert android.mk building system to gradle building system, because I wanted to test the demo source codes in:
https://android.googlesource.com/platform/development/+/05523fb0b48280a5364908b00768ec71edb847a2/samples
But after searching whole internet, I found no one did it yet. So I created this tool by myself. But even with this tool, we couldn't ensure all projects in AndroidSamples could be built and executed successfully because of the API versions and features mismatch. So I created my own projects for https://android.googlesource.com/platform/development/+/05523fb0b48280a5364908b00768ec71edb847a2/samples
And I want to convert those demo projects one by one.
Now the whole source codes are here:
https://github.com/clockzhong/AndroidSamples
I already successfully converted some samples into gradle building system and executed them correctly on my android phones. But I still have some version mismatch issues, anyway, I'll mentioned it in the project check-in comments.

Resources