mobile-dev-inc / mobile-dev-inc/dadb
Dadb.list throws IOException on unauthorized device (OFFLINE)?
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
Exception in thread "main" java.io.IOException: Command failed (host:transport:131xxxxxxx19J): device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
at dadb.adbserver.AdbServer.send$dadb(AdbServer.kt:99)
at dadb.adbserver.AdbServerDadb.open(AdbServer.kt:137)
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:244)
at dadb.Dadb$Companion.list$default(Dadb.kt:243)
at LogcatKt.list(Logcat.kt:36)
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 with Dadb.kt at list and AdbServer.kt at AdbServer.send and AdbServerDadb.open, following the stack trace for unauthorized-device handling. Reproduce with an unauthorized or offline device and determine the intended list behavior; the issue needs that expected outcome and a regression test before the work is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100