Select the necessary tools and install them. (Their location may be different) I`m sorry for the problems you have with this. It seems that Google changed one of the Android SDK licenses today, and this revealed an error, as I wrote the license acceptance script in our Dockerfie. I updated the CircleCI 2.0 image to properly accept the licenses – github.com/circleci/circleci-images/commit/1ac3ee07c1142291cafaf74c21b04fed46016a57 – it was the error – the SDK manager wasn`t updating all the components because the licenses have not yet been accepted. This will of course install ALL available updates, but this will save you some time if you can save space. Sleep should avoid faulty readline in the installation program, as „yes“ does not work properly in this case. From July 2019, the simplest method is to use: the floating doctor –android-licenses in the command prompt. The logic of Android license in the floating doctor is implemented with sdkmanager –licenses, it seems ok. Try cleaning up the Flatter project and opening the Android project with Android Studio.

You can consider it as a purely Android project and check why it happens. I checked, and /opt/android sdk, where Android tools are set up. Both do not contain licenses for file names. What I suspect is that Google may have updated something in the SDK manager – maybe the license text has changed? (Accepted licenses are recorded as the SHA1 hard drive of the license text). Thank you very much esase for the publication of this. I even installed the 7.1.1 (API 25), but no luck. I only installed the SDK platform, Google API and sources for Android SDK. construction was a success.

The problem was due to the fact that I installed Android Sdk on Android Studio and by apt with apt install sdk android sdb adb. Cordova also called the files installed via apt instead of the files in my home directory. I`m working to reproduce it locally so that I can completely unpack it. One thing I would suggest is to install SDK 27 and 27.0.3 construction tools so you can try to get a more meaningful error message – than I did in our CI, at least to tell me what dependencies have actually failed. To check the problem, simply repeat the process related to the licensing issue. If you use tools/bin/sdkmanager licenses – you must always have human interaction. I have the problem with my gitlab CI. This is my solution: $ANDROID-HOME/bin/sdkmanager –licenses –sdk_root-$ANDROID-HOME None of the command line tools worked for me on Windows, but if they went to Tools -> SDK and a different sdK was downloaded, you will be asked to accept licenses.