Fixed
Status Update
No update yet.
Comments
ku...@google.com
je...@google.com
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
am...@google.com
Almost 2 months later and this is still broken
de...@google.com
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
pl...@gmail.com
jb...@google.com What is the update on this?
g....@gmail.com
What is the status of this item?
Description
We have a Gradle plugin that does some bytecode instrumentation.
We still use the deprecated Transform API until we finished the transition to the new ASM API.
However, we have noticed that with AGP 7.2 our bytecode transformation does not work properly anymore when there is also a plugin applied that uses the ASM API.
It appears that something happened between AGP 7.2.0-alpha02 and AGP 7.2.0-alpha03 that changed the way the output of our transform task is linked to the input of the dexBuilder.
As a consequence, our transformed classes are not used.
Please take a look at the attached txt file that shows that the output directory of the transform task is not properly linked on 7.2.
STEPS TO REPRODUCE:
1. open the attached sample project
2. the sample project registers one transformer that uses the old transform API and one that uses the ASM API
3. build the project and take a look at the log output
4. the log output depicts how task outputs and inputs are linked
5. try with AGP version 7.1.3 and 7.2.0 and you will get the result shown in the attached txt file
------------------
Studio Build:
Version of Gradle Plugin: 7.2.0
Version of Gradle: 7.3.3
Version of Java: 11
OS: Win