Context
The kotlin command provisions the Android SDK itself (first android build downloads the SDK into ~/Android/Sdk), but it only CHECKS the SDK license (the checkAndroidSdkLicenseAndroid task fails with "Some licenses have not been accepted"). The only supported way to accept the license is running the separately-installed sdkmanager --licenses, which is an extra tool outside the "kotlin only" workflow and awkward in CI.
The acceptance is just hash files in $ANDROID_HOME/licenses/ (e.g. android-sdk-license = 24333f8a63b6825ea9c5514f83c2829b004d1fee), which are static.
What is needed
A supported way to accept the license from the toolchain itself, e.g.:
- a kotlin command/flag (kotlin sdk --accept-licenses or similar), or
- an option/setting to auto-write the standard license hash files during SDK provisioning, or
- at minimum, documentation of the officially supported non-interactive acceptance path.
Expected behavior
A fresh machine can run kotlin build for an android/app project and have licenses handled by the toolchain (explicitly accepted or documented), without installing sdkmanager.
Context
The kotlin command provisions the Android SDK itself (first android build downloads the SDK into ~/Android/Sdk), but it only CHECKS the SDK license (the checkAndroidSdkLicenseAndroid task fails with "Some licenses have not been accepted"). The only supported way to accept the license is running the separately-installed sdkmanager --licenses, which is an extra tool outside the "kotlin only" workflow and awkward in CI.
The acceptance is just hash files in $ANDROID_HOME/licenses/ (e.g. android-sdk-license = 24333f8a63b6825ea9c5514f83c2829b004d1fee), which are static.
What is needed
A supported way to accept the license from the toolchain itself, e.g.:
Expected behavior
A fresh machine can run kotlin build for an android/app project and have licenses handled by the toolchain (explicitly accepted or documented), without installing sdkmanager.