JitPack构建因Android SDK许可协议失败后自动恢复的原因及解决建议咨询

What caused the automatic fix? #

The most likely reasons for the v1.2 build failure resolving on its own in v1.3 tie back to JitPack's shared build environment:

• JitPack environment updates: Between your v1.2 and v1.3 releases, JitPack’s team may have updated their base build images to include pre-accepted licenses for older Android SDK components (like Android 25 in your case). When v1.3 was built, it used an updated image where the SDK 25 licenses were already approved, eliminating the error.
• Shared build cache: JitPack often reuses cache from other projects that had already installed and accepted licenses for SDK 25. By the time you triggered the v1.3 build, the necessary components and license agreements were already cached on the build machine handling your request.
• Temporary machine inconsistency: JitPack uses a pool of build machines, and it’s possible an outdated machine (without SDK 25 licenses) handled your v1.2 build, while a newer, updated machine processed v1.3. This kind of inconsistency can happen in shared CI/CD environments.

How to fix it if the issue happens again? #

To prevent this flaky build failure from recurring, try these concrete steps:

1. Update your project’s SDK versions to widely supported ones
   Hardcoding old SDK versions (like 25) can lead to compatibility issues with modern CI/CD environments. Update your build.gradle files to use recent, stable versions:

   android {
       compileSdkVersion 33 // Or a newer stable version
       buildToolsVersion "33.0.2"
       
       defaultConfig {
           minSdkVersion 21 // Adjust based on your library's target audience
           targetSdkVersion 33
       }
   }
   

   This reduces reliance on outdated SDK components that may not be pre-configured in JitPack’s environment.

2. Explicitly accept licenses via JitPack configuration
   Create a jitpack.yml file in your project root to force installation and license acceptance for required SDK components:

   before_install:
     - yes | sdkmanager "platforms;android-25" "build-tools;25.0.2"
   

   The yes | prefix automatically answers "yes" to all license prompts, ensuring the necessary components are set up before your build runs.

3. Add license acceptance properties to Gradle
   Add this line to your project’s gradle.properties file to tell Gradle to auto-accept SDK licenses:

   android.sdk.accept.licenses=true
   

   Note this works best with newer Gradle versions, so ensure your project uses a supported Gradle plugin version.

4. Lock dependency versions
   Avoid dynamic version ranges (like +) in your build.gradle files. Use specific, fixed versions for all plugins and dependencies to make your builds more predictable and less prone to environment-related surprises.

内容的提问来源于stack exchange，提问作者Shuwn Yuan Tee