You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.
With the update to Gradle 3.0 and API 26, all builds in CI are failing with the following error -
$ echo no | android create avd --force -n test -t android-19 --abi armeabi-v7a
Error: Target id is not valid. Use 'android list targets' to get the target ids.
The command "echo no | android create avd --force -n test -t android-19 --abi armeabi-v7a" failed and exited with 1 during .
A similar issue was reported to Travis back in May 2017, but they haven't looked into it till now. After trying a lot of different ideas with no luck, we decided to disable running instrumented tests to publish an update.
Moving forward, we need to either find a way to make it work again or migrate this project to a better CI.
The text was updated successfully, but these errors were encountered:
* Updates project to use Android Gradle plugin v3.x and updated all 3rd party deps
* Disables running instrumentation tests in CI, see #56
* Fixes Proguard issue for release builds, updates gradle version
Also, the response builder in OkHttp 3.8 has made the message mandatory which Barricade was not passing, causing IllegalStateExceptions. I've fixed that issue by hardcoding a static message for now. In the future, we could make even the message configurable like we do for status codes.
With the update to Gradle 3.0 and API 26, all builds in CI are failing with the following error -
A similar issue was reported to Travis back in May 2017, but they haven't looked into it till now. After trying a lot of different ideas with no luck, we decided to disable running instrumented tests to publish an update.
Moving forward, we need to either find a way to make it work again or migrate this project to a better CI.
The text was updated successfully, but these errors were encountered: