Building apk also crashes for me. However, building appbundle works.
Running with --release also crashes, but if you run --debug and then --release, it does seem to work (weird one). After succesfully running with --release, you'll be able to build apk.

The Android Gradle LintPerVariantTask now appears to be adding JARs from all build variants to its inputs:
https://android.googlesource.com/platform/tools/base/+/1f9787310d64a66370627a2aaefa1e616565c17d

The libapp.so libraries containing the app's compiled Dart code are packaged in a JAR, and a different JAR is generated for each variant. I'm not sure how dynamically generated per-variant JARs are supposed to be handled if the lint task expects all variants' JARs to be available.

As a hack workaround you could change the lintOptions in app/build.gradle to disable the lint task:

lintOptions {
    checkReleaseBuilds false
}

@blasten

Hi,
It also fails on my side I tried first --debug then --release it fails. I tried checkReleaseBuilds false but many plugin fails like shared_preferences, maps etc all fail to work. What is the best solution ?

Same here. Recently updated android studio, android sdk, gradle and flutter, And I no longer able to build release apk

Hi,
Looks like this is a big issue then. I upgrade all too. Any one found any solution?

I wouldn't consider this a solution, but I've found a workaround. I was having the same issue and tried building --debug and then --release and it still didn't work. However, if you look at the path in your specific error, it should either end with debug/libs.jar or profile/libs.jar. This indicates which apk you need to build first. In OP's case it is debug/libs.jar so building --debug first and then --release worked. In my case, it was profile/libs.jar so building --profile and then --release worked. I'm pretty sure building the --release shouldn't have to access the debug or profile directories though.

TL;DR
If your error says debug/libs.jar, build --debug then --release.
If your error says profile/libs.jar, build --profile then --release.

I downgraded the android gradle and gradle version, from Android studio Project Structure. And Clean build my project. now it is working.

@Jwiggiff

TL;DR
If your error says debug/libs.jar, build --debug then --release.
If your error says profile/libs.jar, build --profile then --release.

That works, thanks!

@Jwiggiff
Yes I compile and install. But many other things dont work example shared preferences, map etc. But they all work perfectly fine in debug mode so meaning there is a bigger bug some where which I think need resolution.

@Jwiggiff

TL;DR
If your error says debug/libs.jar, build --debug then --release.
If your error says profile/libs.jar, build --profile then --release.

Excellent, thanks!

I have flavors in my gradle

If you have flavors, you have to build to project for every single flavor 3 times, once for debug and once for release, and once for profile

@ahmaducg does your method help I dont get it exactly what to do cause now I have even upgrade my android studiio to version 4. What else should I do now down grade it ?

@newbieflutter Downgrading will help, If any of the above methods don't work. You just need to downgrade the Android Gradle and Gradle version, In Project Structure of your android app.

yep downgrading is the solution for now till this gets fixed.

its a bad idea to manually build for each flavor if you say it works. it shouldnt be that way but can be considered a temporary workaround

The Android Gradle LintPerVariantTask now appears to be adding JARs from all build variants to its inputs:
https://android.googlesource.com/platform/tools/base/+/1f9787310d64a66370627a2aaefa1e616565c17d

The libapp.so libraries containing the app's compiled Dart code are packaged in a JAR, and a different JAR is generated for each variant. I'm not sure how dynamically generated per-variant JARs are supposed to be handled if the lint task expects all variants' JARs to be available.

As a hack workaround you could change the lintOptions in app/build.gradle to disable the lint task:

lintOptions {
    checkReleaseBuilds false
}

This worked perfectly for me

The Android Gradle LintPerVariantTask now appears to be adding JARs from all build variants to its inputs:
https://android.googlesource.com/platform/tools/base/+/1f9787310d64a66370627a2aaefa1e616565c17d

The libapp.so libraries containing the app's compiled Dart code are packaged in a JAR, and a different JAR is generated for each variant. I'm not sure how dynamically generated per-variant JARs are supposed to be handled if the lint task expects all variants' JARs to be available.

As a hack workaround you could change the lintOptions in app/build.gradle to disable the lint task:

lintOptions {
    checkReleaseBuilds false
}

@blasten

Even if this worked, some plugins will not work because of R8 and minifying

It appears that task dependencies aren't wired up in Android Gradle plugin 4.0. While this bug is being fixed and changes rolled out, you can either follow the workarounds: #58247 (comment) or #58247 (comment).

Otherwise, continue using the AGP version managed by the Flutter tool as that is the latest version that is known to work well with Flutter.

Otherwise, continue using the AGP version managed by the Flutter tool as that is the latest version that is known to work well with Flutter.

Can you expand on this? How do we know which AGP version is managed by the Flutter tool?

The versions that flutter create sets. One way to find that out is deleting <app>/android/BUILD.gradle and <app>/android/gradle/wrapper/gradle-wrapper.properties and then running flutter create . in the <app> directory.

The Android Gradle LintPerVariantTask now appears to be adding JARs from all build variants to its inputs:
https://android.googlesource.com/platform/tools/base/+/1f9787310d64a66370627a2aaefa1e616565c17d

The libapp.so libraries containing the app's compiled Dart code are packaged in a JAR, and a different JAR is generated for each variant. I'm not sure how dynamically generated per-variant JARs are supposed to be handled if the lint task expects all variants' JARs to be available.

As a hack workaround you could change the lintOptions in app/build.gradle to disable the lint task:

lintOptions {
    checkReleaseBuilds false
}

@blasten

This worked perfectly, thanks

I'm running on debian 9 and the workaround for downgrading to 3.6.3 , then --profile && --release, works for my machine.
thanks heap!

This is still not working on flutter 2.0.6.
Many packages dont support both gradle 3.+ and null safety and we can still not build apps on release mode on gradle 4.+.
The only solution is keep everything outdated in order to be able to build release apk with 3.+.
How is this not fixed yet?

@niktses This issue was filed over a year ago, and is marked closed. If you are still having a problem, please file a new issue with full details and instructions to reproduce it. Thanks!

It is marked as closed while it is not fixed and has over a hundred comments. It makes more sense to me to reopen this. And it is a major issue as well. As i see it as of right now no flutter developer can reasonably release their app while having upgraded to flutter 2.0 and gradle 4.0 that has came out a year ago.

Hi @niktses
This issue was closed as fixed by #71446. If you are still facing it, please file a new issues with the steps to reproduce the issue.
Thank you

This is an issue that has not been fixed for 1.2 year not a new one. This needs to reopen. Me copy pasting the original into a new issue doesn't seem correct.

@niktses We would like to resolve your issue, but we can't do that without a fairly detailed explanation of what you are doing. See @blasten's comment above in #58247 (comment). The best place to put that information is in a new issue so that it will be visible to the team. Thanks!

I really don't get why you don't reopen it. There is not a single word that i would change if i created a new one.

Run flutter create counter
Update the app to use Android Gradle plugin 4.0.0
Run flutter build apk

You can scroll to the top to see more details.

Gradle expects a ../libs.jar for every combination of flavor - buildType (in new project needs 3 - release - debug - profile, in my project needs 48 so the above 'solutions' of running each one once is out of the question especially with dev-op).

This is not a simple issue as it prevents us from releasing an app as the apk is never generated.

Hi @zanderso if you review my issue I logged #81974

You will be able to reproduce the issue of Flutter supporting AGP 4.0.1.

I am still debugging and trying to figure it out, but the gist of it all is that Flutter Tools does not have a reference to the gradle setup, Gradle seems to be dependant on what location in the directory you run it from.

The Command that fails :

/home/gotama/Documents/test_project/android/gradlew -Pverbose=true -Ptarget-platform=android-x86
-Ptarget=/home/gotama/Documents/test_project/lib/main.dart
-Pdart-defines=RkxVVFRFUl9XRUJfQVVUT19ERVRFQ1Q9dHJ1ZQ== -Pdart-obfuscation=false -Ptrack-widget-creation=true
-Ptree-shake-icons=false -Pfilesystem-scheme=org-dartlang-root assembleDebug

In my issue I also show the use of the same Flutter Tools command (flutter run -v) where it can only work manually if run in the android directory, I believe at this point there is something wrong with the way the command is executed via the process manager in flutter tools.

Also adding the -p flag to the command and running it manually from the project root directory works.

I have tried to manipulate the command on dev channel and it shows that flutter tools cant even read the gradlew tasks from the android directory and reads from the project directory which has a .gradle folder but it only has the boiler plate tasks in it.

@Jwiggiff

TL;DR
If your error says debug/libs.jar, build --debug then --release.
If your error says profile/libs.jar, build --profile then --release.

That works, thanks!

This works, I had to do all 3 builds,
first with the --debug flag and then --profile to finally compile in --release mode.

THANKS

I really don't get why you don't reopen it. There is not a single word that i would change if i created a new one.

Run flutter create counter
Update the app to use Android Gradle plugin 4.0.0
Run flutter build apk

You can scroll to the top to see more details.

Gradle expects a ../libs.jar for every combination of flavor - buildType (in new project needs 3 - release - debug - profile, in my project needs 48 so the above 'solutions' of running each one once is out of the question especially with dev-op).

This is not a simple issue as it prevents us from releasing an app as the apk is never generated.

Same issues. I have 2 flavors and when building, the error is this:

* What went wrong:

Execution failed for task ':app:lintVitalDevelopmentRelease'.

> Could not resolve all artifacts for configuration ':app:productionReleaseRuntimeClasspath'.

   > Failed to transform libs.jar to match attributes {artifactType=processed-jar, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.

      > Execution failed for JetifyTransform: /Users/builder/clone/build/app/intermediates/flutter/productionRelease/libs.jar.

         > Transform's input file does not exist: /Users/builder/clone/build/app/intermediates/flutter/productionRelease/libs.jar. (See https://issuetracker.google.com/issues/158753935)

This issue is critical since we only need to perform 1 build instead of 2 or 3 (in the case of @niktses, 48).

Edit:

I'm using the "hack" of calling --debug and --profile and only calling it for the current flavor.

Edit 2:

I got it working using this combo:

android/app/build.gradle

...

project.ext.envConfigFiles = [
        developmentdebug: ".env.development",
        developmentprofile: ".env.development",
        developmentrelease: ".env.development",
        productiondebug: ".env.production",
        productionprofile: ".env.production",
        productionrelease: ".env.production",
]

...

    // TODO: Temp measure - Add 'checkReleaseBuilds false' 
    lintOptions {
        disable 'InvalidPackage'
        checkReleaseBuilds false
    }
...

android/build.gradle

     ...
     dependencies {
        classpath 'com.android.tools.build:gradle:4.1.2' // <-- using gradle +4.0 instead of downgrade
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
         ...
    }
...

*android/gradle/wrapper/gradle-wrapper.properties

...
distributionUrl=https\://services.gradle.org/distributions/gradle-6.7.1-all.zip

CI/CD (config per flavor)

# Build (Debug & profile)

flutter build apk --debug --flavor <flavor>
flutter build apk --profile --flavor <flavor>

This config worked without any issue (yet). @niktses you could try using this if works for you. I haven't tried without using debug or profile.

Edit 3:

We can use the above configuration without this part:

CI/CD (config per flavor)

# Build (Debug & profile)

flutter build apk --debug --flavor <flavor>
flutter build apk --profile --flavor <flavor>

@niktses, you can use the above config omitting the previous part.

If you don't want to mess with your CI/CD configs then just upgrade your Gradle version:

User Android Gradle 7.0.0-alpha14 in your android/build.gradle:

dependencies {
    classpath 'com.android.tools.build:gradle:7.0.0-alpha14'
}

And upgrade your Gradle version to 7.0-rc-1 in android/gradle/wrapper/gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-7.0-rc-1-all.zip

If you don't want to mess with your CI/CD configs then just upgrade your Gradle version:

User Android Gradle 7.0.0-alpha14 in your android/build.gradle:

dependencies {
    classpath 'com.android.tools.build:gradle:7.0.0-alpha14'
}

And upgrade your Gradle version to 7.0-rc-1 in android/gradle/wrapper/gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-7.0-rc-1-all.zip

@pedromassango This did work for me, the approaches from above did not work for me at all. I'm on Flutter 2.2.2.
I don't feel comfortable using alpha and rc versions though and I'm not sure why this issue is closed since this happens still.
My project did not start with flavors, I added them later.

flutter doctor output is:

[✓] Flutter (Channel stable, 2.2.2, on macOS 11.4 20F71 darwin-x64, locale en-CZ)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] IntelliJ IDEA Community Edition (version 2020.2.1)
[✓] VS Code (version 1.54.3)
[✓] Connected device (2 available)

• No issues found!

If you don't want to mess with your CI/CD configs then just upgrade your Gradle version:

User Android Gradle 7.0.0-alpha14 in your android/build.gradle:

dependencies {
    classpath 'com.android.tools.build:gradle:7.0.0-alpha14'
}

And upgrade your Gradle version to 7.0-rc-1 in android/gradle/wrapper/gradle-wrapper.properties:
distributionUrl=https\://services.gradle.org/distributions/gradle-7.0-rc-1-all.zip

@pedromassango This did work for me, the approaches from above did not work for me at all. I'm on Flutter 2.2.2.
I don't feel comfortable using alpha and rc versions though and I'm not sure why this issue is closed since this happens still.
My project did not start with flavors, I added them later.

flutter doctor output is:

[✓] Flutter (Channel stable, 2.2.2, on macOS 11.4 20F71 darwin-x64, locale en-CZ)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] IntelliJ IDEA Community Edition (version 2020.2.1)
[✓] VS Code (version 1.54.3)
[✓] Connected device (2 available)

• No issues found!

It is closed because this is not a Flutter issue but an Android project issue.

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.