Skip to content
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

obsolete transform api with Gradle sync #6

Open
SunnyBe opened this issue Feb 1, 2023 · 5 comments
Open

obsolete transform api with Gradle sync #6

SunnyBe opened this issue Feb 1, 2023 · 5 comments

Comments

@SunnyBe
Copy link

SunnyBe commented Feb 1, 2023

I am currently on Gradle 7.3.1.

This becomes an issue in Gradle 8.0
When I apply the plugin: apply plugin: 'com.huawei.agconnect'

API 'android.registerTransform' is obsolete.
It will be removed in version 8.0 of the Android Gradle plugin.
The Transform API is removed to improve build performance. Projects that use the
Transform API force the Android Gradle plugin to use a less optimized flow for the
build that can result in large regressions in build times. It’s also difficult to
use the Transform API and combine it with other Gradle features; the replacement
APIs aim to make it easier to extend the build without introducing performance or
correctness issues.

There is no single replacement for the Transform API—there are new, targeted
APIs for each use case. All the replacement APIs are in the
androidComponents {} block.

The Transform API uses incremental APIs deprecated since Gradle 7.5. Please add
android.experimental.legacyTransform.forceNonIncremental=true to
gradle.properties to fix this issue. Note that this will run transforms
non-incrementally and may have a build performance impact.
For more information, see https://developer.android.com/studio/releases/gradle-plugin-api-updates#transform-api.
To determine what is calling android.registerTransform, use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
Affected Modules: app

@huan721
Copy link
Contributor

huan721 commented Feb 3, 2023

the APMS uses the transform API.
If you do not use the APMS, stop it temporarily. If you use the APMS, do not upgrade to JDK11.
After the next version of the AGC is released, the APMS of the AGC will be compatible with gradle7 + jdk11.
But this tip will not be eliminated for that time.
We plan to adapt to gradle8.0 in March. After the adaptation finished, this message will not be displayed.

@huan721
Copy link
Contributor

huan721 commented Feb 24, 2023

We plan to adapt to gradle8.0 in March 2023.
After the adaptation is complete, this prompt will not be displayed.

@SunnyBe
Copy link
Author

SunnyBe commented Feb 28, 2023

Thank you. I look forward to the new update.

@SunnyBe
Copy link
Author

SunnyBe commented May 3, 2023

I just checked the changelogs here: CHANGELOGS and didn't find the expected update. Let me know if I am checking the wrong place.
Any ideas when this could be ready, so I can manage expectations with my team?

@Pittvandewitt
Copy link

As a workaround you could consider adding apmsInstrumentationEnabled=false to your gradle.properties file. This will disable HTTP/HTTPS network request monitoring, but you will be allowed to upgrade to gradle 8.0. More information can be found here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants