This repository has been archived by the owner on Jan 22, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1k
AutoParcel/AutoValue error with kapt and the latest android gradle plugin (3.0.0-beta7) #59
Comments
Getting the same error for AGP rc 1 when doing
|
I see in your repo you have removed the following line in the app/build.gradle
In order to compile the sample you have to add it, but with the new keyword
|
Any news about this? I'm facing the same issue. Thanks! |
What worked for me was to declare the dependency as both |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I can't seem to get the
android-auto-parcel
sample to work with Android Studio 3.0 beta and the newest Android gradle plugin. Please see my fork of this repo for an example commit to demonstrate this issue here. I originally found this issue with my own project trying to implement a simple AutoValue object (so this might be an AutoValue/Kotlin/kapt issue and not apply here...)Steps to reproduce in any AutoValue project:
kapt
dependencyThe first error I get is related to the dependency API name changes in 3.0.0:
Trying to fix that, I remove the
provided "frankiesardo:auto-parcel:$autoparcel_version"
depdency declaration (sincekapt
should cover it) and I get this new error:Reading the AS 3.0 migration guide, I see that
provided
is replaced withcompileOnly
, so I tried swapping that out (compileOnly "frankiesardo:auto-parcel:$autoparcel_version"
) and that gives me the same first error I had previously...Additionally, I found a post on stackoverflow that seems like the same problem, which recommended adding the following to the
defaultConfig
section:but that doesn't seem to help the issue either.
What am I missing here? Is this an AutoValue error? or a Kotlin error? Or is there a simple fix for the 3.0.0 plugin that I've overlooked? I appreciate any help here!
(also clean builds don't seem to affect the error output)
The text was updated successfully, but these errors were encountered: