Credit to @Grsmto As per this blog post you need to open a terminal and launch the following commands sequentially: UPDATE Now the workaround it’s easier, you just need to go to Build -> Clean Project and then sync. Windows gradlew clean gradlew assemble Linux/Mac ./gradlew clean ./gradlew assemble then sync the project.
It’s because you messed up the dependencies. You have to either fully migrate to AndroidX dependencies or stay on Support library ones. Thus, instead of implementation “android.arch.persistence.room:runtime:$room_lib” annotationProcessor “android.arch.persistence.room:compiler:$room_lib” use implementation “androidx.room:room-runtime:2.0.0-alpha1” annotationProcessor “androidx.room:room-compiler:2.0.0-alpha1” Also be sure to check your gradle.properties project file to contain android.useAndroidX=true android.enableJetifier=true Jetifier helps libraries, which depend on old Support … Read more
For some reason, running gradle in daemon mode causes a null console object. If you specify the appropriate command line flag, ./gradlew assembleRelease –no-daemon it’ll work.
For Android gradle plugin 1.1.2+ (com.android.tools.build:gradle:1.1.2+) libraryVariants – does not work anymore use: task javadoc(type: Javadoc) { source = android.sourceSets.main.java.srcDirs classpath += project.files(android.getBootClasspath().join(File.pathSeparator)) destinationDir = file(“../javadoc/”) failOnError false } destinationDir = file(“../javadoc/”) – locate javadocs at root of project directory (in this way jenkins javadoc plugin could find it and show in special Document panel) … Read more
It could be that the gradle-2.1 distribution specified by the wrapper was not downloaded properly. This was the root cause of the same problem in my environment. Look into this directory: ls -l ~/.gradle/wrapper/dists/ In there you should find a gradle-2.1 folder. Delete it like so: rm -rf ~/.gradle/wrapper/dists/gradle-2.1-bin/ Restart IntelliJ, after that it will … Read more
If you are using the Gradle Wrapper (the recommended option in Android Studio), you enable stacktrace by running gradlew compileDebug –stacktrace from the command line in the root folder of your project (where the gradlew file is). If you are not using the gradle wrapper, you use gradle compileDebug –stacktrace instead (presumably). You don’t really … Read more
Since you have the classes under 2 different packages, these are totally different classes. So the classes aren’t replacing each other. With flavors, you can’t override class files. So, one way to accomplish what you want is move these classes out of main, and into flavorA. So you would have something like this: project/ | … Read more
Simply testCompile is the configuration for unit tests (those located in src/test) and androidTestCompile is used for the test api (that located in src/androidTest). Since you are intending to write unit tests, you should use testCompile. Update: The main distinction between the two is the test sourceset runs in a regular Java JVM, whereas the … Read more
open the Build Variants pane, typically found along the lower left side of the window: set debug to release shift+f10 run!! then, Android Studio will execute assembleRelease task and install xx-release.apk to your device.
Just create a file called gradle.properties in your root project: root |–gradle.properties |–build.gradle |–settings.gradle |–app |—-build.gradle Then add inside the file: org.gradle.jvmargs=-Xmx2048m