![]() To honour the JVM settings for this build a new JVM will be forked. In that case you need to manually start SDK Manager and add the build-tools and accept license. ![]() It could be that it is a higher version of build-tools that is missing. ![]() If you find from the error message what is your builds current build-tools version. Unfortunately the way as OP originally solved it does not always work. CI works fine though - not sure what the difference is. Which does not mean it will work if you have not installed the android tools yet and have already accepted the latest license(s).ĮDIT: Saying that, it still does not work on my test gubuntu box until I link the SDK up to AS. SDK auto-download: Gradle will attempt to download missing SDK packages that a project depends on. I guess that official tools would not want to skip this step for legal reasons. I was surprised at first that this didnt work out of the box, even when I had accepted the licenses for the named components via the android tool, but it was pointed out to me its the SDK manager inside AS that creates the /licenses folder. The hashes are sha1s of the licence text, which I imagine will be periodically updated, so this code will only work for so long :)Īnd install it manually, but it is the gradle's new feature purpose to do it. This would have the same result as the process outlined in the link of the error msg ( ). To recreate the current $ANDROID_HOME/license folder on you machine. Jake Wharton pointed out to me that you can currently use mkdir -p "$ANDROID_SDK/licenses"Įcho -e "\n8933bad161af4178b1185d1a37fbf41ea5269c55" > "$ANDROID_SDK/licenses/android-sdk-license"Įcho -e "\n84831b9409646a918e30573bab4c9c91346d8abd" > "$ANDROID_SDK/licenses/android-sdk-preview-license" I have encountered this with the alpha5 preview.
0 Comments
Leave a Reply. |