adb server version (41) doesn't match this client (39); killing...
Two different adb binaries are running — e.g. Android Studio’s SDK adb and another one on PATH (Homebrew, Genymotion, older SDK).
Seen on:
Android
Meaning
Each client restarts the server with its own version, so devices disconnect repeatedly. Use one adb everywhere.
Common causes
- Multiple adb installations on PATH
- Tools bundling their own adb (Genymotion, Vysor, scrcpy)
- Old platform-tools
⚡ Quick fix
- Find all adb binaries: which -a adb
- Point PATH and tools to the SDK’s platform-tools/adb
- Update platform-tools
Detailed fix by platform
Shell
- kotlin
which -a adb export PATH="$HOME/Library/Android/sdk/platform-tools:$PATH" adb version
How to diagnose
- Binaries — which -a adb
- Tools — Which app ships its own adb?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- ActivityNotFoundException ActivityNotFoundException: Unable to find explicit activity class; have you declared this activity in your AndroidManifest.xml?
- adb unauthorized adb: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set
- author identity unknown Author identity unknown *** Please tell me who you are.
Most viewed in Android
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026