-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Dagger 2.38 breaks build with AGP 7.0.0-beta05 #2762
Comments
@julioromano Did you mean beta05? Seeing this issue in 7.0.0-beta05
|
Oh yes, edited accordingly. Brainfart on my side. |
Same error with 7.0.0-rc01 |
+1 |
Reflect into the property getter since the return type is different between earlier betas and RC but we are only interested that they return a com.android.build.api.variant.Component implementation. This change also adds a few deprecation suppressions to old variant APIs and old transform APIs usages, these are deprecated but we keep using them for backwards compatibility reasons. Fixes #2762 RELNOTES=Fix an incompatibility issue with AGP 7.0.0-beta05 and 7.0.0-rc01 PiperOrigin-RevId: 386974233
Reflect into the property getter since the return type is different between earlier betas and RC but we are only interested that they return a com.android.build.api.variant.Component implementation. This change also adds a few deprecation suppressions to old variant APIs and old transform APIs usages, these are deprecated but we keep using them for backwards compatibility reasons. Fixes #2762 RELNOTES=Fix an incompatibility issue with AGP 7.0.0-beta05 and 7.0.0-rc01 PiperOrigin-RevId: 386974233
A 2.38.1 release will be done soon that contains this fix along with the fix for #2784. |
Is this applicable to 7.0.0? |
@VincentJoshuaET Yes |
Downgrading to AGP 7.0.0-beta04 solves the issue.
Dagger's 2.38 release notes do say that any version older than AGP 7.0.0-beta04 would break, but beta05 is newer.
The text was updated successfully, but these errors were encountered: