Inspect the version that actually runs
./gradlew --version
Compare the output with gradle/wrapper/gradle-wrapper.properties. If they appear inconsistent, check which repository and wrapper script the shell or CI job invoked. Nested Android projects can have their own wrapper.
Select a compatible target
Read the selected AGP compatibility table before choosing a Gradle version. “Newest Gradle” is not automatically the right distribution for an older Android plugin or third-party build plugin.
The wrapper documentation describes the supported upgrade procedure, distribution types and verification options.
Update the wrapper as a set
A typical update command uses an explicit reviewed version:
./gradlew wrapper --gradle-version <compatible-version>
Replace the placeholder before execution. Follow the current wrapper guidance to refresh all required wrapper files and commit the relevant scripts, JAR and properties. Do not change only the URL and assume every wrapper component has been updated.
Verify download integrity and CI behavior
Use the publisher's documented distribution checksum where supported. Review changes to the wrapper JAR and scripts as executable build infrastructure, not as harmless metadata.
| Check | Evidence |
|---|---|
| Correct distribution | ./gradlew --version output |
| Correct JVM | Same output plus CI Java configuration |
| Reproducible invocation | CI calls the committed wrapper |
| Compatible build | Release and verification tasks succeed |
Keep rollback practical
Retain the previous committed wrapper and plugin combination until the new toolchain is validated. APKLint's Build Analyzer can review version declarations and errors, but it cannot verify a downloaded distribution or execute your private build. The decisive evidence is the committed wrapper and the actual local/CI output using it.
Sources and further reading
Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
