IssueTracker

I have the same thing...

Hi,

Please try the links given below for solution

http://stackoverflow.com/questions/33404552/execution-failed-for-task-appcompiledebugjavawithjavac-in-android-studio

where it has some solution "export JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home""

Just check it.

https://github.com/patrickvankann/spring-halbuilder/issues/12

http://stackoverflow.com/questions/26476149/java-lang-nosuchmethoderror-com-google-common-collect-fluentiterable-tolistlc

https://developer.jboss.org/thread/261469?start=0&tstart=0

Dear amruthav links you provided is irrelevant to this issue. Issue occurs after android app build gradle update(from 2.1.0-alpha4 to 2.1.0-alpha5). In our project, we do not use guava. So in this case guava - compile time dependency that used by DataBindings processor.

If you need addition information please let me know.

[Comment deleted]

I'm on Windows, these solutions can not solve this problem, and I can't back to alpha4 now, sad...

So my soultion was to rollback to Android Studio 2.1 preview 4 to be able to switch to gradle plugin 2.1.0-alpha4

My solution for now is adding guava dependency in gradle, provided 'com.google.guava:guava:19.0', it works.

Hi,

Please provide your sample code which reproduces the issue. zip and share

Don't forget to explain the steps to reproduce the issue with your code. is it just by building your code or something else?

Note: Please upload the attachments to google drive and share the folder to android-bugreport@google.com, then share the link here.

provided guava dependency works, thanks

Also seeing this in 2.1.0-alpha5 in relation to databinding classes. Project is using Dagger2 and android-apt which may or may not be relevant from reading posts above.

Same issue. Also using dagger2 and databinding

Same issue. I'm using dagger2 and databinding. I also have guava 19.0 included in my project, but I still have the same issue. I'm reverting to alpha4 in the meantime.

After checking with a new project, I have not found issues with gradle plugin (v2.1.0-alpha5) nor have I found issues with databinding. The issue seems to be with either dagger compiler or with android apt (I'm thinking the latter).

the source for recreating the issue is available from https://github.com/Avinash-Bhat/as-bug-205589

Looks like the issue is with dagger codegen (doing the build using --stacktrace)

The stacktrace is attached.

also maybe the version of the google-collect artifact maybe not as required, looks to me like the dagger codegen expects that to be of version 18 or above, whereas the classpath is only providing the version 17 or below. (the method in question (append) was added in v18).

The issue is fixed by using dagger 2.1

For the ones using Dagger, I can confirm nashp...@gmail.com proposal of upgrading to 2.1 solves the issue

I have solved the issue by upgrade Dagger to 2.2 version

I confirm that this issue was affecting Dagger version 2.0.2 and has been resolved in dagger 2.2

On a separate note, I was using Dagger 2 Subcomponents which changed the way how they are connected to the parent so one might get misleading errors when simply upgrading to 2.2

[Comment deleted]

I'm still getting this issue when using com.android.tools.build:gradle:2.1.0 and dagger 2.2 does not fix it. I have a simple project here that can be used to reproduce it:

https://github.com/futurice/android-rxmvvmdi

Note that the project is set to use com.android.tools.build:gradle:2.0.0 so it currently compiles. You need to switch it to 2.1.0 to reproduce the error.

For me the problem was compiling the tests. Temporary workaround:
testCompile 'com.google.guava:guava:19.0'

[Comment deleted]

[Comment deleted]

Same error for me here. Using dagger 2.2, but it doesn't get fixed when switching to 2.1. Using Android Studio 2.2 Preview 1 and android plugin 'com.android.tools.build:gradle:2.2.0-alpha1'

Using the brand new line in order to run the dagger compiler processor at build time:
annotationProcessor 'com.google.dagger:dagger-compiler:2.2'

It does not seem to be working properly tho

[Comment deleted]

* What went wrong:
Execution failed for task ':app:transformJackWithJackForDebug'.
> com.android.jack.ir.JNodeInternalError: java.lang.Exception: java.lang.NoSuchMethodError: com.google.common.collect.FluentIterable.append([Ljava/lang/Object;)Lcom/google/common/collect/FluentIterable;

...

Caused by: java.lang.RuntimeException: com.android.jack.ir.JNodeInternalError: java.lang.Exception: java.lang.NoSuchMethodError: com.google.common.collect.FluentIterable.append([Ljava/lang/Object;)Lcom/google/common/collect/FluentIterable;
  at com.android.jack.api.v01.impl.Api01ConfigImpl$Api01CompilationTaskImpl.run(Api01ConfigImpl.java:126)

Issue is still present for both Dagger 2.1 and Dagger 2.2

As a work around try this

http://stackoverflow.com/questions/23413126/nosuchmethoderror-hashcode-fromstring-when-using-com-android-tools-buildgradle

Still happening on same conditions with the new gradle 2.2.0-alpha2 for dagger 2 :(

[Comment deleted]

Also happening for me on `build:gradle:2.1.2` (stable) and `dagger:2.5`

Unfortunately, adding `dagger 2.1` as suggested there did not resolve the issue for me. But I have found temporal work-around:
Adding apt 'com.google.guava:guava:19.0' just above dagger-compiler makes it compiles without error.
https://github.com/google/dagger/issues/356#issuecomment-228015108

This happens to me too when I use Dagger 2.6. Adding Guava only to use Dagger 2.6 and for no other reason is no option for me with a method count of about 15000 methods. Are there any news on this issue?

I have the same issue: errors when compile DataBinding after adding
apt 'com.google.dagger:dagger-compiler:2.7' with apt version:
'com.neenbedankt.gradle.plugins:android-apt:1.8', Android Studio 2.2, Gradle 2.14.1

A lot of things have changed in this area with 3.0. Please file a new bug if you still have issue with the new annotation support.