Android "compileSdkVersion is not specified" in CI

By Kaveh Alemi·Latchkey

The Android Gradle plugin needs a compile SDK to know which android.jar to compile against. When compileSdk is missing from the module build file, configuration fails because the platform cannot be resolved.

What this error means

The build fails with "compileSdkVersion is not specified. Please add it to build.gradle" or "compileSdk is not specified."

> compileSdkVersion is not specified. Please add it to build.gradle

Common causes

No compileSdk in the module build file

The android {} block omits compileSdk, so the plugin has no platform to compile against.

A variable for the SDK resolved to nothing

A compileSdk set from a project property or catalog that is empty leaves the value unspecified at configuration time.

How to fix it

Declare compileSdk in the module

1. Add compileSdk to the module android {} block.
2. Ensure the matching SDK platform is installed on the runner.
3. Re-run the build.

android {
  compileSdk = 34
}

Install the platform in CI

Make sure the chosen compile SDK platform is present so the plugin can resolve android.jar.

- run: sdkmanager "platforms;android-34"

How to prevent it

• Set compileSdk explicitly in every Android module.
• Install the matching SDK platform on the runner.
• Verify catalog or property values for the SDK are non-empty.

Frequently asked questions

Related guides

References

• Apache Maven guides
• Gradle user manual
• GitHub Actions documentation