adb: device 'emulator-5554' not found

[alirezaeiii]

Here is my scrip to start the emulator :

name: Android Instrumentation Test
on:
  push:
    branches:
      - main
  pull_request:
    branches:
      - main

jobs:
  android_test:
     name: Running Android Tests
     runs-on: macos-13
     continue-on-error: true
     steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Set up JDK 17
        uses: actions/setup-java@v4
        with:
          java-version: 17
          distribution: 'adopt'

      - name: Change wrapper permissions
        run: chmod +x ./gradlew

      - name: Setup Android SDK
        uses: android-actions/setup-android@v3

      - name: Start Android Emulator
        uses: reactivecircus/android-emulator-runner@v2
        with:
           api-level: 33
           target: default
           arch: x86_64
           profile: Nexus 4
           emulator-options: -no-window -no-boot-anim -no-audio -no-snapshot-load
           script: |
            adb wait-for-device
            adb shell input keyevent 82
           ./gradlew connectedAndroidTest --continue

      - name: Upload Test Reports
        if: failure()
        uses: actions/upload-artifact@v4
        with:
          name: android-test-report
          path: '**/build/reports/androidTests/connected/'

It seems device is booted successfully.
When it want to run test, it prints :

Execution failed for task ':features:feature-setting:connectedDebugAndroidTest'.
> com.android.builder.testing.api.DeviceException: No connected devices!

I am runnung on macOS 13, so why this happens? Is it something wrong in my script for Github Action?

Here is the sample : https://github.com/alirezaeiii/TMDb-Compose-Playground

[poponuts]

I had a similar issue. Can someone have a look at this?

The process '/usr/local/lib/android/sdk/platform-tools/adb' failed with exit code 1
  /usr/local/lib/android/sdk/platform-tools/adb -s emulator-5554 shell getprop sys.boot_completed
  adb: device 'emulator-5554' not found

[alirezaeiii]

@poponuts I resolved my issue by using lower api level : https://github.com/alirezaeiii/TMDb-Compose-Playground/blob/main/.github/workflows/android-test.yml

[eXpl0it3r]

We're running into this issue as well: https://github.com/SFML/SFML/actions/runs/11134310092/job/30953377901#step:25:76

Lowering the emu API level to 26 doesn't seem to work and even if it did, seems more like a workaround than a fix. Maybe the issue should be reopened: https://github.com/SFML/SFML/actions/runs/11151778634/job/30995995208

Maybe GitHub changed something on the image, which trips up the emulator from starting...

[alirezaeiii]

I agree @eXpl0it3r , It is just a workaround not a fix. I reopen the issue.

[zhkvdm]

Any updates? I have the same issue. With 26 image it works well. After update to 29 image android tests fails.
Emulator is connected

adb devices -l
List of devices attached
emulator-5554          device product:sdk_gphone_x86 model:Android_SDK_built_for_x86 device:generic_x86 transport_id:1

But tests failed

> Task connectedDebugAndroidTest FAILED
adb: device 'emulator-5554' not found
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task 'connectedDebugAndroidTest'.
> com.android.builder.testing.api.DeviceException: No connected devices!

And also command adb shell settings fails. Try to call it after adb devices

adb shell settings list global
adb: device 'emulator-5554' not found

[ychescale9]

I was able to run it successfully with API 31 on macos https://github.com/ReactiveCircus/android-emulator-runner/actions/runs/11202425213/job/31138520013 though it's much slower than the Linux runners.

Unless your job strictly requires running on macOS, I suggest using the linux runners and enable KVM if you can.

[BeyondEvil]

Well, we're seeing this on a large Linux (x64) runner as well...

Operating System
  Ubuntu
  22.04.5
  LTS
Runner Image
  Image: ubuntu-22.04
  Version: 2024[10](https://github.com/cosafe/Cosafe-app/actions/runs/11449489773/job/31855174618#step:1:11)15.1.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20241015.1/images/ubuntu/Ubuntu2204-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20241015.1

Configure emulator
  API level: 29
  target: google_apis
  CPU architecture: x86_64
  Hardware profile: pixel_6_pro
  Cores: 2
  RAM size: 4096M
  Heap size: 
  SD card path or size: 256M
  Disk size: 
  AVD name: test
  force avd creation: true
  Emulator boot timeout: 600
  emulator port: 5554
  emulator options: -no-metrics -no-window -gpu swiftshader_indirect --read-only -no-snapshot -noaudio -no-boot-anim -camera-back none
  disable animations: true
  disable spellchecker: false
  disable Linux hardware acceleration: false
  enable hardware keyboard: false
  Channel: 0 (stable)

Also, KVM isn't available on large arm64 runners.

[BeyondEvil]

Just tried it with regular "ubuntu-22.04" and seeing the same error.

[jcuervo-almato]

sill facing this issue...

[kieyanmamicheOtO]

Any updates on this issue? I am facing the same problem myself. On an ubuntu-22.04 large 8-core runner

[SilverPreeceSOF]

Were people in this thread seeing any errors further up? I do get this error, but it appears to be caused by the AVD not being created successfully in an earlier step:

   /usr/bin/sh -c \echo no | avdmanager create avd --force -n test --abi 'default/x86' --package 'system-images;android-27;default;x86' --device 'Nexus 5' --sdcard '64MB'
  Loading local repository...                                                     
  [=========                              ] 25% Loading local repository...       
  [=========                              ] 25% Fetch remote repository...        
  [=======================================] 100% Fetch remote repository...       
  Error: AVD not created.
  null
  ::endgroup::
::group::Terminate Emulator
Terminate Emulator
  /usr/local/lib/android/sdk/platform-tools/adb -s emulator-5554 emu kill
  error: could not connect to TCP port 5554: Connection refused

It seems to me that better debugging output would help a lot with the various issues with this action. I will open a separate issue for that.

[clark-ewerton]

hi @alirezaeiii @eXpl0it3r @ychescale9 @BeyondEvil @poponuts @SilverPreeceSOF @jcuervo-almato @kieyanmamicheOtO

Apparently I think I found the root cause of this:

this emulator-options "emulator-options: -no-window -no-boot-anim -no-audio -no-snapshot-load" seem to mess everything up.

I just removed them from the workflow, and the device was detected by ADB. Besides that, the API version issue might also be related, but it didn't affect me.

I was able to run my Android tests successfully using Ubuntu and Maven. Here's the workflow for reference: https://github.com/clark-ewerton/mobile-test-automation-lab/blob/main/.github/workflows/cicd.yml

Also I just would like to give a huge thumbs-up for @easabbir, I just found an example of this solution on his github and it was a lifesaver: https://github.com/easabbir/appium-actions/blob/master/.github/workflows/demo-android.yml