We found the same problem building the project on Jenkins. With buildToolsVersion `25.0.2`, we have to accept licenses before creating. In our case, we had to run: there is a small delay between Yesses, so the order with the license could be suspended for a while, but it does not require human intervention. Warning: File /Users/mtro.josevaler-strong text-io/.android/repositories.cfg could not be loaded. 6 out of 6 SDK package licenses are not accepted. License checks that have not been accepted (y/N)? Y A sweater request has been created for licenses to be accepted by default. When I say it still doesn`t work on my gubuntu test box until I can connect the SDK to AS. The CI works well – not sure what the difference is… Would those of you who have problems (and don`t use the api-28 image) try to run this in front of anything else? 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 order: You haven`t accepted the licensing agreements for the following SDK components: [Google Repository]. Before you create your project, you must accept the licensing agreements and complete the installation of the missing components with android Studio SDK Manager. Alternatively, you can learn how to transfer license agreements from one workstation to another, and go d.android.com/r/studio-ui/export-licenses.html If you have this problem for a native React app, in addition to the steps above, make sure you have the local.properties file in your app`s Android directory, which refers to your `sdk` directory: Make sure you`ve installed the last Android SDK first.
Second, make sure ANDROID_HOME is fixed. (echo $ANDROID-HOME) Remember: run these commans with the same user as jenkins. In our Debian, user Jenkins is just jenkins. In other words, if you do it as root, the accepted licenses will be created as root, so Jenkins doesn`t read them. I solved this problem, installed these components in “Android 7.0 (API 24)”: SDK platform Google Apis Sources for Android SDK yes | sdkmanager licenses – which accepts new licenses that have not yet been accepted In July 2019, the simplest method is to use: flatterer doctor–android-licenses in the order invitation. Hello. I had the same problem. I solved it by accepting (1) the licenses and (2) the “Licences” folder in my sdk folder (as explained here: developer.android.com/studio/intro/update) The utility sdk manager will guide you through licenses that must be accepted.
To check the problem, simply repeat the process related to the licensing issue. | sdkmanager –update that accepts licenses for the sdkmanager manager himself, and then I documented completely the information in the following article: Accept the Android SDK license via Android Studio yes | sudo/Library/Android/sdk/tools/bin/sdkmanager –licenses $ANDROID-HOME/bin/sdkmanager –licenses –sdk_root-$ANDROID-HOME NB: This led to the immediate acceptance of the SDK license and the construction worked from there. I was initially surprised that it didn`t work out of the box, even though I had accepted licenses for components named via the Android tool, but I was told that it was the SDK manager within AS who created the folder/licenses. You did not accept the following SDK licensing agreements, the way to accept licensing agreements on the order line has changed. You can use the SDK manager called: Accept the android-sdk-license-c81a61d9` [y/n] license: y after this installation was successful. But if you use Gradle 3.1 to create, here`s what`s on display. You have not accepted the licensing agreements of the following SDK components: [Android SDK Platform 23, Android SDK Build Tools 23.0.1].