Flutter integration_test "No devices found" in CI

Flutter integration tests run on a real device, emulator, or simulator. If none is connected when flutter test integration_test or flutter drive runs, Flutter reports "No supported devices connected" and no test executes.

What this error means

The command fails with "No supported devices connected" or "No devices found with name or id matching ...". flutter devices lists nothing runnable in the job.

No supported devices connected.
Run 'flutter emulators' to list and start any available device emulators.

Common causes

No emulator/simulator was started

The job runs the integration tests without first booting a device, so Flutter has no target.

The device booted after Flutter checked

An emulator launched but had not finished booting, so flutter devices saw nothing ready.

How to fix it

Boot a device and wait before the test

1. Start the emulator/simulator in the job.
2. Wait until it is booted (adb ... sys.boot_completed or simctl boot).
3. Then run the integration tests, optionally with -d.

adb wait-for-device
adb shell 'while [[ -z $(getprop sys.boot_completed) ]]; do sleep 1; done'
flutter test integration_test -d emulator-5554

Run inside an emulator action

Run the Flutter integration tests within an emulator runner so the AVD is booted first.

- uses: reactivecircus/android-emulator-runner@v2
  with:
    api-level: 34
    script: flutter test integration_test

How to prevent it

• Boot a device and wait for readiness before integration tests.
• Run inside an emulator action that gates on boot.
• Confirm flutter devices shows a target first.

Related guides