mobile-dev-inc / mobile-dev-inc/dadb
Crash with Command failed (host:features): more than one device/emulator
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
I am using DADB but it fails with Command failed (host:features): more than one device/emulator
Exception in thread "main" java.io.IOException: Command failed (host:features): more than one device/emulator
at dadb.adbserver.AdbServer.send$dadb(AdbServer.kt:99)
at dadb.adbserver.AdbServerDadb.open(AdbServer.kt:138)
at dadb.adbserver.AdbServerDadb.<init>(AdbServer.kt:128)
at dadb.adbserver.AdbServer.createDadb(AdbServer.kt:52)
at dadb.adbserver.AdbServer.listDadbs(AdbServer.kt:81)
at dadb.adbserver.AdbServer.listDadbs$default(AdbServer.kt:60)
at dadb.Dadb$Companion.list(Dadb.kt:251)
at dadb.Dadb$Companion.list$default(Dadb.kt:250)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with more than one device or emulator, then trace the stack from Dadb.kt lines 250-251 into AdbServer.kt lines 99, 128, and 138. Compare the host:features request path with the multi-device scenario; done means the reported crash is resolved and the relevant behavior is covered by a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- devtools, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100