-
Notifications
You must be signed in to change notification settings - Fork 64
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
Java.lang.NoSuchMethodError: com.squareup.javapoet.TypeName.isBoxedPrimitive()Z #64
Comments
Your version of JavaPoet is being resolved incorrectly on the Adding apt 'com.squareup:javapoet:1.7.0' first will fix this |
Whenever I've seen someone report it, it was because Dagger 2.2 bundles On Thu, 26 May 2016, 22:40 Jake Wharton, notifications@github.com wrote:
|
Let's all agree to stop using Dagger 2.2! Dagger 2.4 people! On Thu, May 26, 2016 at 4:49 PM Gabriel Ittner notifications@github.com
|
Even
EDIT: apt with auto-value-parcel 0.2.1
apt with auto-value-parcel 0.2.2
|
I'm using Dagger 2.4, Adding javapoet:1.7.0 solved the problem. Commenting it back, problem back. Thanks :) |
If that can help
|
I ran into the same issue. You can downgrade to dagger 2.0.2 unless you need the bleeding edge. |
So the solution here is to upgrade to Dagger 2.4. I'm going to close this as there is nothing for us to do. |
The solution is to add : I was already using dagger 2.4 on my code when the bug came out. |
Nevermind issue seem be because of I keep getting this error: java.lang.NoSuchMethodError:
|
As outlined, the problem is dagger. You need to add |
When I have this in my dependencies I get the error. I
|
Try adding |
thx that works. |
I've observed the error when I had an incorrect AutoValue'd class definition, for example when my Builder definition does not match the data class definition. Correcting the AutoValue definition fixed the error. This was the error reported:
My definition incorrectly had: I was using:
|
Hi,
I tried to update to the latest 0.2.2 and I have this error while compiling.
I use those AutoValue versions:
Everything ok on 0.2.1
The text was updated successfully, but these errors were encountered: