mobile-dev-inc / mobile-dev-inc/dadb
Discover returns an error
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
Hi guys,
I'm Victor, and I'm trying to run the library in a poc application to know how to use it. But the first method that I'm trying is "discover", but it returning me a FileNotFoundException
I'm doing:
fun discover(){
try {
val result = Dadb.discover("localhost")
binding.tvcommandline.text = "" + result.toString()
}catch (ex: java.lang.RuntimeException){
binding.tvcommandline.text = "Failed to discover emulator. No adb device found"
ex.printStackTrace()
}
}
The error is:
Caused by: java.io.FileNotFoundException: .android/adbkey: open failed: ENOENT (No such file or directory)
Some advice?
I'm testing on a Samsung S20 Ultra with Android 12 and connected via USB.
Thank you
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 Dadb.discover("localhost") on the reported Android 12 and USB-connected Samsung S20 Ultra setup. Trace the resulting FileNotFoundException for .android/adbkey and review the existing issue discussion; done means discover handles this setup without the reported failure or clearly reports the required condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100