That`s not to say it works if you haven`t installed Android tools yet and you`ve already accepted the latest licenses. This requires you by each license that you have not yet accepted, and you can simply enter to accept each one. One day, he`ll ask you for a license agreement, press it. Then you have to remove the angle platform. You may need to continue to copy license files to other storage locations depending on the installation. Then I deleted the system files that were no longer used: apt delete android-sdk adb. The Android tool has now become obsolete in favor of the new sdkmanager. Please read Joe Lawson`s response and the following articles from March (2017). Enter an attempt to repeat and rebuild, always give jenkins «unreased licenses», then you must give full permission for your repertoire `sdk` and all its superior repertoires. Here`s the command: then run the sdkmanager command –licenses, it asks to accept licenses. Yes, I`m not. sdkmanager –update that accepts licenses for the sdkmanager manager himself, then @SKempin simply run $ANDROID-HOME/tools/bin/sdkmanager «platforms;android-26» and accept it. Case: contribution: – cp -r Licenses/.
$ANDROID-HOME/licenses` From: developer.android.com/studio/intro/update.html#download-with-gradle I solved this problem by creating a public git repository with the license files accepted. Then I use wget to retrieve these licenses on any computer I need in a [sdk-dir]/licenses directory before running ./ gradlew to create my project. to recreate 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). If you install updates, you will be asked to accept the license agreement. Accept the license agreement and install the updates and you are all set. This will update your Android SDK and accept the license at the same time (z.B. for Android 25: I tried all the commands mentioned above on the Windows 10 machine, but the solution was to check the SDKMANAGER and accept the purchase of licenses Installing missing versions and accept the license (however, in my case, I did not have to do this) If anyone is still with the problem, then please follow the link to the solution aboutreact.com/you-have-not-accepted-the-license-agreements-of-the-following-sdk-components/ We found the same building problem on Jenkins.