-
Notifications
You must be signed in to change notification settings - Fork 58
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
Fixed AGP 8.3.0
breaking change
#154
Conversation
Can you update the Gradle version(s) in checks matrix so the tests can pass? |
Can you provide better actionable feedback? Which versions of Gradle should we be targeting? I've checked locally, and
It seems my changes didn't introduce this issue, but rather this project needs more active contributions. Is it even maintained? Fixing the whole build should be addressed in a separate PR, not in this one. |
I thought it was broken with your update, but seems to just be broken in general. I'll see if I can get it fixed. |
Actually, I have it fixed locally already. The main offender is the After removing it, and therefore the I just submitted #158 fixing the build |
Closing in favor of #159 |
What has changed
Addresses #153 with a minimal set of changes to unblock the consumers of this plugin.
The breaking change is produced because the plugin is accessing an internal AGP API for getting the Android SDK location.
As suggested by @SimonMarquis, this can be done with a public API in
BaseExtension.sdkDirectory
. I made minimal changes to read from there, falling back to anANDROID_HOME
environment variable if not provided to keep the coupling at the bare minimum.Additionally, I've moved the whole
ANDROID_GRADLE_PLUGIN
dependency as acompileOnly
to avoid leaking it to the consumersWhy was it changed
Because since
AGP 8.3.0
, the internal API signature has changed, and it breaks: #153Related issues
AGP 8.3.0 fails with NoSuchMethodError #153
Note
This project is a bit outdated on its dependencies:
A bump to
8.3.0
was not possible without also bumpingGradle
to at least8.4
, and doing so introduced a new problem with accessing a removed API