The new Android machine image, “android:202102-01,” is now available to all CircleCI users. This Ubuntu-based image supports nested virtualization, enables x86 Android emulator-based testing, including UI tests, and comes with the SDK pre-installed. Like other Linux machine images on CircleCI, the Android image can be run on the Linux machine executor.
Check out the blog for details on how to set up an Android testing pipeline with the image.
I was trying to migrate our jobs to the android machine and was running into an issue.
We use fastlane for our builds and the issue we are having is with the fastlane bundletool plugin on the new Android machine. Everything works just fine on docker with the Android image and locally running the lane.
[22:06:02]: Downloading bundletool (0.14.0) from https://github.com/google/bundletool/releases/download/0.14.0/bundletool-all-0.14.0.jar...
"Something went wrong when downloading bundletool version 0.14.0. \nError message\n No such file or directory @ rb_sysopen - https://github.com/google/bundletool/releases/download/0.14.0/bundletool-all-0.14.0.jar"
I have some questions about The new Android machine image, “android:202102-01”:
Can I use it on CircleCI Server?
Can I use it with version 2.0 in config.yml?
I try run example code, but I received the error below:
Creating a dedicated VM with android:202102-01 image
failed to create host: Image android:202102-01 is not supported
Thanks for reaching out! To answer your questions in the order you asked them:
1. Yes, this should work in CircleCI Server
2. In our documentation example, we explicitly specify version 2.1 config: Using Android Images with the Machine Executor - CircleCI
3. We had an issue with this version initially, but there was a fix pushed in November 2021 to solve the issue. I hope that it is working for you now, or please give it another shot if you haven’t yet.
I hope this information is useful, please feel free to create a support ticket if you have additional questions!
EDIT: I do apologize as I received conflicting information after I made this post. For our server instances, Android is not yet available. We are in the process of adding this functionality in a future update, so please be on the lookout for that.
> Could not get resource 'https://jitpack.io/cn/aigestudio/wheelpicker/WheelPicker/1.1.2/WheelPicker-1.1.2.pom'.
> Could not HEAD 'https://jitpack.io/cn/aigestudio/wheelpicker/WheelPicker/1.1.2/WheelPicker-1.1.2.pom'.
> Read timed out
I am thinking this might come from repositories having downtime issues, but on our machines we can access the repos without any issues. Is this an internet/connectivity issues on the machine running the tests/ builds?
Thanks for any clue.
EDIT: Seems to be working now all of sudden. was probably a repository downtime. thanks anyways.