While Android Studio Updated to v3.3 getting API 'variant.getAssemble()' is obsolete and has been replaced with 'variant.getAssembleProvider()'
variant.assemble has been deprecated and replaced by a new provider API.
If for example you are using it as next:
variant.outputs.all { output ->
variant.assemble.doLast {
....
}
}
}
Then replace it the new provider API:
variant.outputs.all { output ->
variant.getAssembleProvider().configure() {
it.doLast {
....
}
}
}
It's a warning, it doesn't negatively impact your build. You may go forward and update to AGP 3.3.0.
The new Android Gradle Plugin started leveraging lazy configuration (Task Configuration Avoidance API and Provider API) which, if used properly, may improve build speeds by only evaluating tasks and properties which are needed. Consumers of AGP need to use the updated API (e.g. getAssembleProvider().configure() instead of getAssemble()) otherwise the tasks and properties are always evaluated.
The point of lazy API: Don't configure tasks which aren't going to run in a particular build.
Read more:
- https://docs.gradle.org/4.10/userguide/lazy_configuration.html
- https://docs.gradle.org/4.10/userguide/task_configuration_avoidance.html
What to do
If it's not coming from your code there's nothing for you to do other than wait for updated libraries (and pray they do it right).
If it comes from your code, here's an example of migration: I'm using this bit of code from Jake Wharton to disable BuildConfig.java generation for my library modules.
libraryVariants.all {
it.generateBuildConfig.enabled = false
}
Using the new lazy API it looks like this.
libraryVariants.all {
it.generateBuildConfigProvider.configure {
it.enabled = false
}
}
The eager API would cause the generateBuildConfig task to be configured even if I didn't need it, such as running clean. The lazy API configures the task only if it's part of the task graph to run. This saves time during the configuration phase.
How to figure out if it comes from your code? Put this in your gradle.properties
android.debug.obsoleteApi=true
Now run a build and check the output for stack traces.
Full error
For completeness, here's an example of a full error message caused by the Fabric plugin 1.27.0 with AGP 3.3.0:
WARNING: API 'variant.getExternalNativeBuildTasks()' is obsolete and has been replaced with 'variant.getExternalNativeBuildProviders()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getExternalNativeBuildTasks(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
Bad example
Here's a diff of how Facebook React dealt with the API migration in their plugin: https://github.com/facebook/react-native/pull/23103/files
In other words, they didn't. taskProvider.get() is equal to task - both uses are eager. The tasks are always configured.
The only thing this approach achieves is removing the warning so
- the consumer has no idea they're not getting any benefits of the lazy API,
- the plugin author is no longer reminded they're using it wrong.
The Task Configuration Avoidance API docs contain a migration guide and a helpful table describing how to create and chain tasks lazily. If you're a plugin author, please read it.
I had the same Warning!!
And this is my app level gradle file:
apply plugin: 'com.android.application'
android {
compileSdkVersion 28
defaultConfig {
applicationId 'com.lauszus.facerecognitionapp'
minSdkVersion 16
targetSdkVersion 28
versionCode 6
versionName '1.2.3'
vectorDrawables.useSupportLibrary = true
ndk {
stl 'c++_static'
cFlags '-std=gnu++11 -fexceptions -frtti -DANDROID_STL=c++_static'
}
setProperty('archivesBaseName', rootProject.name + '-' + defaultConfig.versionName)
}
splits {
abi {
enable true
reset()
universalApk true
include 'armeabi-v7a', 'arm64-v8a', 'x86', 'x86_64'
}
}
project.ext.abiCodes = ['armeabi-v7a':1, 'arm64-v8a':2, 'x86':3, 'x86_64':4]
applicationVariants.all { variant ->
variant.outputs.each { output ->
def baseAbiVersionCode = project.ext.abiCodes.get(output.getFilter(com.android.build.OutputFile.ABI))
// Because abiCodes.get() returns null for ABIs that are not mapped by ext.abiCodes,
// the following code does not override the version code for universal APKs.
if (baseAbiVersionCode != null) {
output.versionCodeOverride = baseAbiVersionCode * 1000000 + variant.versionCode
}
}
if (variant.getBuildType().isMinifyEnabled()) {
variant.assemble.doLast {
variant.mappingFile.renameTo(variant.mappingFile.parent +
"/$archivesBaseName-$variant.baseName-mapping.txt")
}
}
}
signingConfigs {
release
}
buildTypes {
debug {
jniDebuggable true
externalNativeBuild {
ndkBuild {
arguments 'NDK_DEBUG=1', 'NDEBUG=null'
}
}
}
release {
shrinkResources true
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
signingConfig signingConfigs.release
}
}
externalNativeBuild {
ndkBuild {
path 'src/main/cpp/Android.mk'
}
}
lintOptions {
abortOnError false
}
}
dependencies {
implementation 'com.android.support:appcompat-v7:28.0.0'
implementation 'com.android.support:design:28.0.0'
implementation project(':opencv')
}
// These values are all set in my global gradle.properties file
if (project.hasProperty('storeFile') && project.hasProperty('storePassword') &&
project.hasProperty('keyAlias') && project.hasProperty('keyPassword')) {
android.signingConfigs.release.storeFile = file(storeFile)
android.signingConfigs.release.storePassword = storePassword
android.signingConfigs.release.keyAlias = keyAlias
android.signingConfigs.release.keyPassword = keyPassword
} else {
android.buildTypes.release.signingConfig = null
}
If your app level gradle file contains variant.assemble.doLast block then; Try changing “variant.assemble.doLast” to “variant.assembleProvider.get().doLast”
like this:
if (variant.getBuildType().isMinifyEnabled()) {
variant.assembleProvider.get().doLast { //HERE
variant.mappingFile.renameTo(variant.mappingFile.parent +
"/$archivesBaseName-$variant.baseName-mapping.txt")
}
}
referred web link.