Skip to content

Conversation

@emersion
Copy link
Contributor

Google hasn't published an AOSP version of the Android system image for API level 36 yet:
https://issuetracker.google.com/issues/432143095

Temporarily switch to the Google APIs variant to workaround this issue.

@HamdaanAliQuatil
Copy link
Collaborator

HamdaanAliQuatil commented Oct 26, 2025

Log from the failed workflow:
Failed to find package 'system-images;android-36;google_apis;x86'

We'll have to mention the architecture type explicitly, as mentioned in #226

There's an open PR trying to solve this (#227), but the workflow fails there as well, perhaps because of missing libvulkan.so and libX11 libraries for the emulator.

@emersion emersion force-pushed the android-ci-default-workaround branch from 7ab19e5 to df37833 Compare October 26, 2025 15:24
@emersion
Copy link
Contributor Author

Ah, yes. Unfortunately this is tricky to debug since workflows in my PRs aren't run by default and need manual action from project members.

I think missing Vulkan/X11 libs are a red herring, and I think the error is caused by a device name mismatch: android doesn't exist, android-x64 does. I've updated my PR to use the correct device name.

@emersion emersion force-pushed the android-ci-default-workaround branch from df37833 to 807db7f Compare October 26, 2025 15:32
@emersion
Copy link
Contributor Author

Hm, maybe android-x64 isn't the right one, trying gphone64

@HamdaanAliQuatil
Copy link
Collaborator

gphone64 didn't work as well.

No supported devices found with name or id matching 'gphone64'.

Google hasn't published an AOSP version of the Android system image
for API level 36 yet:
https://issuetracker.google.com/issues/432143095

Temporarily switch to the Google APIs variant to workaround this
issue.
@emersion emersion force-pushed the android-ci-default-workaround branch from 807db7f to 11a5e36 Compare October 26, 2025 16:05
@emersion
Copy link
Contributor Author

Okay, one more try with emulator, since the device is named emulator-5554 and prefixes are allowed… Failing that, we could try to remove -d or downgrade to API level 35 (which has an AOSP image available).

@HamdaanAliQuatil
Copy link
Collaborator

I believe this worked. Now we need to bump kotlin version to 1.8.10

@emersion
Copy link
Contributor Author

Added more commits to modernize dependencies.

@emersion emersion changed the title Workaround missing default system image for Android API level 36 Workaround missing Android image in CI and upgrade dependencies Oct 26, 2025
@emersion
Copy link
Contributor Author

Looks like it worked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants