I've started getting following error after updating to AS 3.0 beta 6. Has anyone else come across this? I'm only seeing this error when I try to build/run from AS.....no issue if I run gradle on command line.
* What went wrong:
Execution failed for task ':app:transformDexArchiveWithDexMergerFor<BuildVariantName>Debug'.
> com.android.build.api.transform.TransformException: java.lang.IllegalStateException
Thanks to #Nabin in the comments we found out that enabling Instant Run fix that issue.
Unfortunately - other than the original poster - we had the same issue on the command line. Which means our CI doesn't run.
We found out that we can disabling the incremental dexing by setting the flag -Pandroid.useDexArchive=false. See here for more infos:
A new incremental dexing pipeline has been implemented. Now the Gradle plugin dex only the class files that have changed. It is enabled by default, but you can disable it by doing one of the following:
Passing -Pandroid.useDexArchive=false when running builds from command line e.g. ./gradlew :app:assembleDebug -Pandroid.useDexArchive=false.
Adding android.useDexArchive=false to the gradle.properties file in your root project.
Luckily we don't need incremental dexing on our CI.
Unfourtnaly it doesn't help us in Android Studio with disabled Instant Run!
Related
Build apk failed in Travis CI. But sometimes it can build successfully, especially in night. I'm not sure it is a network error or other reasons.
SEVERE: APKit-AdkInstrumentor(1): extracting the apk failed rc = 1
Throwable occurred: aC: extracting the apk failed rc = 1
at aG.a(SourceFile:199)
at aG.a(SourceFile:155)
at aG.a(SourceFile:150)
at v.a(SourceFile:142)
at e.f(SourceFile:181)
at e.<init>(SourceFile:88)
at a.<init>(SourceFile:27)
at com.dynatrace.android.instrumentation.AdkInstrumentor.c(SourceFile:337)
at com.dynatrace.android.instrumentation.AdkInstrumentor.main(SourceFile:277)
Instrumentation failed
Task :mobile:autoInstrumentStagUnpinnedRelease FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':mobile:autoInstrumentStagUnpinnedRelease'.
Process 'command '/home/travis/build/app-android/mobile/build/tmp/prepareApkit/dynatrace-mobile-agent-android-7.2.4.1262/Android/auto-instrumentor/instrument.sh'' finished with non-zero exit value 5
if you are sure the build is working fine sometimes, I think it may be related to the third party of the application ( I think you want to make sure the Dynatrace Gradle plugin, you should clean and sync your project works successfully then check with Travis-ci configuration)
also, need to check does Travis-ci support this kind of application related to third-party applications
as seen from the link
https://answers.dynatrace.com/questions/213065/auto-instrument-apk-failed.html
You are still using the auto-instrumentor version 7.1.10.2332. If you are using the Dynatrace Gradle plugin, you should clean and sync your project. This behavior should force Android Studio to use the new plugin version.
To troubleshoot your problem we need the full log file. The problem occurs in a 3rd party tool and the root cause is not visible in the stack trace.
Task :react-native-device-info:compileReleaseJavaWithJavac FAILED
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':react-native-device-info:compileReleaseJavaWithJavac'.
java.io.FileNotFoundException: /workspace/eos-native/node_modules/react-native-device-info/android/build/intermediates/annotation_processor_list/release/annotationProcessors.json (No such file or directory)
The error makes sense , and the file is not there, but I have no idea why its not there? It is created when I run a debug version of the app and debug versions of my libraries, react-native-device-info, react-orientation-locker etc.. I've cleaned, gradle synched, rebuilt etc. but when trying to assemble or install a release build I get this error within seconds. What is causing the Java
I had the same problem in an android project (without react) when I added a library module.
After searching for a solution for quite some time, I finally deleted the .gradle directory in the project root folder.
This solved the problem for me.
update android gradle plugin to 3.3
update gradle to 4.10.3
fixed the issue for me.
I'm working on an Android project with two projects inside it. When trying to run a build with gradlew (./gradlew build), I see the following error:
Execution failed for task ':example:lint'.
Could not initialize class
com.android.build.gradle.tasks.Lint$LintGradleIssueRegistry
With stacktrace enabled, this is listed as a java.lang.NoClassDefFoundError.
Oddly, the first time I ran this (which downloaded dependencies), the build failed with a different error:
Execution failed for task ':example:lint'.
lombok/ast/Node
The gradle wrapper that Android SDK created for the project is using Gradle 2.8.
Could this be a configuration issue with the project or my dev machine? I'm trying to avoid using the Android SDK lint tool as this complains about the projects using Gradle (and I hear it may miss some parts of these projects).
Turned out this was a configuration issue in our build.gradle. The following line had been added for testing and never removed:
configurations.classpath.exclude group: 'com.android.tools.external.lombok'
As such, the classes needed for linting were missing.
The following discussion pointed us in the right direction, in case it's useful to anyone else:
https://github.com/evant/gradle-retrolambda/issues/96
I am trying to run a Gradle Android task generated by libGDX utility (the desktop task runs fine) in IntelliJ IDEA, but I'm only getting this nonspecific error message. What is the issue, or where are the logs, or how to enabled logs?
Information:Gradle: Executing tasks: [:core:assemble, :android:assembleDebug]
Information:24. 10. 2015 16:58 - Compilation completed with 1 error and 0 warnings in 9s 415ms
Error:Gradle: Execution failed for task ':android:proguardDebug'.
> java.io.IOException: Please correct the above warnings first.
PS: Not sure if it is relevant, but I have modified build files and ProGuard file to support Scala as described there.
I did not find a way of getting any useful logs from IntelliJ IDEA. I solved the problem by running Gradle from console.
gradlew assemble --stacktrace --info
Problem was Gradle could not find tools.jar. Adding system environment variable JAVA_HOME pointing to Java SDK directory fixed the issue.
I am using local gradle of version 2.4 and IntelliJ IDEA 14.1.3
When I run project from IntelliJ it runs fine but when execute gradle clean build command from command line it gives the flowing exception and build fails.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:mockableAndroidJar'.
> java.util.zip.ZipException: invalid entry compressed size (expected 2051 but got 2050 bytes)
This looks like an old ques which is not yet answered yet.
I got into same problem, when my jar files could not be read by Android Studio and it gave me the above mentioned error.
Taking lead from the comment by -Mikhail Boyarsky I changed classpath in build.gradle file to 'com.android.tools.build:gradle:2.2.3'.
Synced project and it started working.
I solved it by changing com.android.tools.build:gradle:2.3.0 version to 2.2.3, then build it with another exception and then I changed the version back to 2.3.0.
Not sure how it works, looks like a gradle bug.