Gradle version error

[burekas7]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

Hi,

Why do I get this error in "Install Dependencies"

What went wrong:

An exception occurred applying plugin request [id: 'com.android.application']

> Failed to apply plugin 'com.android.internal.version-check'.

   > Minimum supported Gradle version is 8.2. Current version is 8.1.1. If using the gradle wrapper, try editing the distributionUrl in /Users/builder/clone/android/gradle/wrapper/gradle-wrapper.properties to gradle-8.2-all.zip

When my file shows:

distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-8.2-all.zip
networkTimeout=10000
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists```


### Build id (optional)

6796169f712ec7fc4101cd63

[dam-ease]

Hello @burekas7,
Please can you confirm this file is in the PATH below in your project:

android/gradle/wrapper/gradle-wrapper.properties

[JamesMcIntosh]

@dam-ease This is coming from the Gradle which is bundled with the image, not the use's app
/Users/builder/clone/android/gradle/wrapper/gradle-wrapper.properties

/Users/builder/programs/gradle-8.1.1/bin/gradle wrapper --gradle-version 8.7 --distribution-type bin

[JamesMcIntosh]

Hi Damilola,

Is there some sort of "optimization" in the Install Dependencies step which tries to start this gradle daemon?

My gradle file has:

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-8.7-all.zip

The logs below demonstrate that it is attempting to use gradle version 8.7 as in my configuration but it is bootstrapping it using the locally installed 8.1.1 version.

> flutter packages pub get
.....

Got dependencies!
137 packages have newer versions incompatible with dependency constraints.
Try `flutter pub outdated` for more information.

> /Users/builder/programs/gradle-8.1.1/bin/gradle wrapper --gradle-version 8.7 --distribution-type all
Starting a Gradle Daemon (subsequent builds will be faster)
> Task :gradle:compileJava NO-SOURCE
> Task :gradle:compileGroovy
> Task :gradle:pluginDescriptors
> Task :gradle:processResources
> Task :gradle:classes
> Task :gradle:jar

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/builder/clone/android/app/build.gradle' line: 2

* What went wrong:
An exception occurred applying plugin request [id: 'com.android.application']
> Failed to apply plugin 'com.android.internal.version-check'.
   > Minimum supported Gradle version is 8.4. Current version is 8.1.1. If using the gradle wrapper, try editing the distributionUrl in /Users/builder/clone/android/gradle/wrapper/gradle-wrapper.properties to gradle-8.4-all.zip

[JamesMcIntosh]

Seems strange to be using the locally installed gradle at all. Gradle always recommends using the wrapper.
Any idea why it uses a global one rather than the one located in android/gradlew?

[dam-ease]

Hello @JamesMcIntosh,
Apologies for the delay in response!
Yes, it might be making use of the default gradle version i.e. (8.1.1 pre-installed on the machine) if you don't have Gradle wrapper in your repo (gradlew file). This is a common issue in Flutter because the app template previously doesn't include Gradle wrapper files by default. You need to add and push them to the repo to be able to control Gradle version on any CI/CD. By adding them, I mean removing /gradlew from your .gitignore file.

[JamesMcIntosh]

gradlew is already in the android folder, did you also see the two questions in the comments below?
https://github.com/orgs/codemagic-ci-cd/discussions/2944#discussioncomment-12241257

[dam-ease]

Hey @JamesMcIntosh,
Yes, please. I'll respond as a reply there as well.

[awaisjamil-mp]

facing the same issue any workarround???

[JamesMcIntosh]

Hi @awaisjamil-mp,
For my build it is not fatal as it doesn't stop the install dependencies step from completing, (which it probably should fail the build).
The build step uses the correct gradle version to produce the build as it's resolved from the build.
If you want to work around it you're going to have to manually upgrade the global install of gradle in the post clone script.

James

[JamesMcIntosh]

Hi @dam-ease,

Are you going to escalate this issue? There are two concerns here:

1. Identify why there is a gradle deamon started after the flutter dependencies have been successfully resolved.
2. Why the build doesn't fail if there is a fatal error reported during install dependencies.

[dam-ease]

Hey @JamesMcIntosh,
We have observed this behavior and have been able to reproduce it in the past. One suggested approach to controlling the Gradle version on any CI/CD system, is to remove /gradlew from the .gitignore file in the Android folder. The Flutter template automatically adds this entry, which can sometimes cause inconsistencies in Gradle versions across different environments.

The Gradle daemon starts to speed up subsequent builds. Even if dependencies are resolved, Gradle still needs to manage tasks like compiling native Android code, and generating APK/AAB files.
Regarding why the build doesn’t fail even if a fatal error occurs during dependency installation, it’s likely that the project still manages to build using the pre-installed version of Flutter. This means the process continues despite the reported error.

Currently, I'm unable to reproduce the issue when /gradlew is included in android/.gitignore, but it’s worth trying to remove it and run the build again.