Raw CI log shows Flutter flags the emulator as “unsupported”.

Our Android CI job boots an x86 (32-bit) emulator on API 28. Recent Flutter toolchains don’t support 32-bit x86 emulators, so flutter devices lists the emulator as “unsupported (emulator)” and tests abort before they run.

Evidence (from logs):

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

The following devices were found:
Android SDK built for x86 (mobile) • emulator-5554 • unsupported • Android 9 (API 28) (unsupported) (emulator)

Our workflow uses reactivecircus/android-emulator-runner@v2 without overriding arch, whose default is x86 (32-bit). Flutter’s supported Android architectures are x64 (x86_64), Arm32, Arm64 and not 32-bit x86.

Flutter 3.29 release notes explicitly removed the android-x86-jit-release artifact, reinforcing that x86 (32-bit) isn’t a viable target.

Proposed fix:
In the workflow, explicitly specify a 64-bit emulator architecture and perhaps update the API level as well.
The arch input parameter provided by reactivecircus/android-emulator-runner@v2, defaults to x86. We should explicitly choose x86_64 instead.