Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Android image API 22 → 24 #476

Closed
wants to merge 1 commit into from
Closed

Conversation

ilammy
Copy link
Collaborator

@ilammy ilammy commented May 24, 2019

Let's try fixing the Android build which turned red recently.

The image distributed by SDK Manager for API 22 seems to be broken and results into issues like this during emulator startup:

emulator: ERROR: This AVD's configuration is missing a kernel file! Please ensure the file "kernel-ranchu" is in the same location as your system image.

It seems that the distributed kernel file is named "kernel-qemu" instead of "kernel-ranchu". However, renaming the kernel file still produces issues like this:

emulator: ERROR: New emulator backend requires minimum kernel version 3.10+ (currently got lower)
Please make sure you've got updated system images and do not force the specific kernel image together with the engine version

Given that Android Lollipop is no longer supported by Google (support ended in March 2018), let's update to Android Nougat emulator with API level 24.

The image distributed by SDK Manager for API 22 seems to be broken
and results into issues like this during emulator startup:

    emulator: ERROR: This AVD's configuration is missing a kernel file! Please ensure the file "kernel-ranchu" is in the same location as your system image.

It seems that the distributed kernel file is named "kernel-qemu"
instead of "kernel-ranchu". However, renaming the kernel file still
produces issues like this:

    emulator: ERROR: New emulator backend requires minimum kernel version 3.10+ (currently got lower)
    Please make sure you've got updated system images and do not force the specific kernel image together with the engine version

Given that Android Lollipop is no longer supported by Google (support
ended in March 2018), let's update to Android Nougat emulator with
API level 24.
@ilammy ilammy added O-Android 🤖 Operating system: Android infrastructure Automated building and packaging labels May 24, 2019
@ilammy ilammy requested review from vixentael and Lagovas May 24, 2019 14:57
@vixentael
Copy link
Contributor

Hopefully it will help 🤞

@ilammy
Copy link
Collaborator Author

ilammy commented May 24, 2019

Hopefully it will help 🤞

Well, it does help with the emulator actually starting up instead of aborting early. However Android system does not seem to boot up properly (on CircleCI and in my local Docker environment alike). It seems that this issue will require more black magic than usual.

@ilammy
Copy link
Collaborator Author

ilammy commented May 28, 2019

Well, it seems that latest emulators have received a big bunch of new bloat, so they take ages to boot up. I've been waiting for mine for 40 minutes and it still is not ready (CircleCI has a 10-minute limit).

I have also tried images for other API levels (both higher and lower) but with the same result: they do not seem to boot up in timely manner. I wonder whether this is some new issue, or just me doing it wrong.

CircleCI recommends using Firebase Test Lab for Android. Maybe that would be worth exploring as an alternative.

@ilammy
Copy link
Collaborator Author

ilammy commented Sep 9, 2019

Well, this approach obviously does not work right off the bat, so let's close this PR. I'm currently exploring another CI service for mobile platforms. Hopefully, it will support Android better.

@ilammy ilammy closed this Sep 9, 2019
@ilammy ilammy deleted the ilammy/android-update branch June 8, 2020 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Automated building and packaging O-Android 🤖 Operating system: Android
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants