Status Update
Comments
xa...@google.com <xa...@google.com> #2
The main issue is ProjectInfo.getProject()
which leaks the project, and the services is exposes everywhere, when we need to control how certain things are allocated.
For instance, inside the VariantProperty
objects, all the Gradle Property
instance must be initialized a certain way so we expose this via VariantPropertiesApiServices
. Exposing the Project
will lead (and has already led) to people instantiating them manually and doing it wrong.
It is probably fine to expose some aspect of Project
in ProjectInfo
as long as we don't expose Project
itself.
sa...@google.com <sa...@google.com> #3
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Chipmunk Canary 6 (2021.2.1.6)
- Android Gradle Plugin 7.2.0-alpha06
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
je...@google.com <je...@google.com>
xa...@google.com <xa...@google.com>
xa...@google.com <xa...@google.com> #4
There are still a few deprecated items in ProjectInfo
that needs to be fixed.
hm...@google.com <hm...@google.com>
hm...@google.com <hm...@google.com> #5
All file based APIs have been removed now and replaced with lazy provider based ones in this class. Only deprecated method left is createTextResources() which supports the BaseVariant.getApplicationIdTextResource() API which is targeted to be removed in 9.0 at which point that method can be cleaned up too
an...@google.com <an...@google.com> #6
The fixes for this issue are now also available in:
- Android Studio Koala Feature Drop | 2024.1.2 Canary 6
- Android Gradle Plugin 8.6.0-alpha06
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Description
It should not exist.