I checked ~/.android and/opt/android sdk where Android tools are used. Both do not contain folders named licenses. to create the current $ANDROID_HOME/license folder on your computer. This would have the same result as the process described in the msg error link (tools.android.com/tech-docs/new-build-system/license). или попробуйте это : yes | sudo sdkmanager –licenses yes | sudo sdkmanager –licenses Hello together, so after I broke my head, I discovered that the first place you need to check is your environment variables to check the Android home path. Follow it from there and update the necessary SDKs in your SDK Manager. What was my problem was that I had an earlier version of Android Studio that I had removed, so my path was different for the new one and I also had Embarcadero in another path, so I updated in one SDK manager, but Ionic 2 used the other where I hadn`t updated and accepted the licenses. If you have the same problems, you just need to copy the new files in both paths for them to be reflected. Just my 2 cents. I hope it helps someone else. Learn more: stackoverflow.com/questions/40383323/cant-accept-license-agreement-android-sdk-platform-24/40383457#40383457 Unfortunately, the way the operation was originally resolved doesn`t always work. If you find from the error message what your Builds latest version of building tools is. It may be a higher version of building tools that is missing.

In this case, you must manually launch the SDK Manager and add the building tools and accept the license. I added this: E: android-sdk_r24.4.1-windows android sdk-windows tools; E:android-sdk_r24.4.1-windowsandroid sdk-windowsplatform-tools We found sdk managers under /var/lib/jenkins/tools/android-sdk/tools/bin. If your isn`t there, you`ll find it with find/name “sdkmanager” I use plugin cordova push plugin for push notifications I installed Google Repository and Google Play Services packages by Android SDK Manager, but every time I run ionic Build Android to create Build, it gives me the following errors. Remember: run these commans with the same user as jenkins. In our Debian, the Jenkins user is just jenkins. In other words, if you do it as root, the accepted licenses are created as root, so Jenkins won`t read them. The Android tool has become obsolete in favor of the new sdk manager. Please follow Joe Lawson`s response and subsequent contributions as of March (2017).

If you use tools/bin/sdkmanager –licenses, you still need human interaction. I have a problem with my Gitlab CI. That`s my solution: you can solve that. Please open platforms/Android in Android Studio. Then, the same error is displayed in the build protocol as an error. You will find the link to the agreement missing. You can simply click on it to download and accept it. I may be late, but it helped me accept SDK licenses for OSX, thanks guys, it worked. But in my env sdkmanager –update fails. Here`s my quick hack job. – Run: yes| sdkmanager –licenses – run : yes | sdkmanager –update || Exit 0 Voila! You have accepted the SDK licenses and you can get started. I had already updated on the command line and I guess the Android SDK manager has a more comprehensive way to dissolve dependencies, including the license.

To update the selected packages, click Resume or OK, and then accept all license agreements. My circleCI configuration for Android has now been running successfully for a few weeks, but all of a sudden today all builds fail with it: I was initially surprised that it doesn`t work out of the box, even when I accepted the licenses for the mentioned components via the Android tool, but I was told that this is the SDK manager in AS, that creates the /licenses folder. Give a ticket for rehearsal and build, Jenkins always gives “licenses not accepted”, so you need to give full permission to your “sdk” directory and all higher directories….