Android build error: unknown packet filter

Question

update: It may seem interesting that I also got a similar error:
"Error: ignoring unknown packet filter" extra-android-m2repository "" on this line:

android update sdk --filter extra-android-m2repository --no-ui --force > /dev/null 

but I decided that he updated the sdk tools to rev. 23. The original error is saved.

---

I have an Android build job running on the continuous integration of travis.ci. He used to work, but recently he started to give an error:
"Error: ignoring unknown packet filter 'sysimg-19'"

in this line:

 echo yes | android update sdk --all --filter sysimg-19 --no-ui --force > /dev/null 

which then causes the avroid command to fail for the avd command:
"Valid ABI: no ABI. Error: invalid --abi armeabi-v7a for the selected target.

I also tried this without the -all flag, but this leads to the same result.
I believe the reason may be some changes to the Android SDK that I don’t know about. Someone tell me what the problem is?

See my full travis.yml below.

Travis.yml:

 language: java jdk: - oraclejdk7 android: components: - build-tools-19.1.0 env: matrix: - ANDROID_TARGET=android-19 ANDROID_ABI=armeabi-v7a before_install: # Install base Android SDK - sudo apt-get update -qq - if [ `uname -m` = x86_64 ]; then sudo apt-get install -qq --force-yes libgd2-xpm ia32-libs ia32-libs-multiarch > /dev/null; fi - wget http://dl.google.com/android/android-sdk_r22.6.2-linux.tgz - tar xzf android-sdk_r22.6.2-linux.tgz - export ANDROID_HOME=$PWD/android-sdk-linux - export PATH=${PATH}:${ANDROID_HOME}/tools:${ANDROID_HOME}/platform-tools # install android build tools - wget https://dl-ssl.google.com/android/repository/build-tools_r19.1-linux.zip - unzip build-tools_r19.1-linux.zip -d $ANDROID_HOME - mkdir -p $ANDROID_HOME/build-tools/ - mv $ANDROID_HOME/android-4.4.2 $ANDROID_HOME/build-tools/19.1 # Install required components. # For a full list, run `android list sdk -a --extended` # Note that sysimg-19 downloads only ARM, because only the first license query is accepted. - android list sdk -u --all --extended - echo yes | android update sdk --all --filter platform-tools --no-ui --force > /dev/null - echo yes | android update sdk --all --filter build-tools-19.1.0 --no-ui --force > /dev/null - echo yes | android update sdk --all --filter android-19 --no-ui --force > /dev/null - echo yes | android update sdk --all --filter sysimg-19 --no-ui --force > /dev/null - echo yes | android update sdk --filter extra-android-support --no-ui --force > /dev/null - echo yes | android update sdk --filter extra-android-m2repository --no-ui --force > /dev/null # Create and start emulator - echo no | android create avd --force -n test -t $ANDROID_TARGET --abi $ANDROID_ABI - emulator -avd test -no-skin -no-audio -no-window & - chmod +x gradlew before_script: - adb wait-for-device - adb shell input keyevent 82 & script: - TERM=dumb ./gradlew -s connectedCheck 

Answer 1

I found a solution myself: Due to renaming system images in Android SDK line

 - echo yes | android update sdk --all --filter sysimg-19 --no-ui --force > /dev/null 

it should be:

 - echo yes | android update sdk --all --filter sys-img-armeabi-v7a-android-19 --no-ui --force > /dev/null 

To fix another issue with extra-android-m2repository, it was resolved when I updated the sdk tools to version 23:

 - wget http://dl.google.com/android/android-sdk_r23-linux.tgz - tar xzf android-sdk_r23-linux.tgz