PeaceDefener
PeaceDefener

Reputation: 638

ADB server didn't ACK on macOS

I am getting this error since two days ago when I updated my Android Studio to the latest stable version 2.3; the full error message I am getting from Gradle Console is:

07:59:59 E/adb: error: could not install *smartsocket* listener: Address already in use
07:59:59 E/adb: ADB server didn't ACK
07:59:59 E/adb: * failed to start daemon *
07:59:59 E/adb: error: cannot connect to daemon
07:59:59 E/ddms: '/Users/USER_NAME/Library/Android/sdk/platform-tools/adb start
server' failed -- run manually if necessary

My attempts to solve the issue:

Environment:

Upvotes: 20

Views: 19457

Answers (5)

Edward Tan
Edward Tan

Reputation: 954

In my case, I had an old version of adb installed using brew cask. And while I updated my Android Studio to the latest, the adb was still pointing to the brew installed older version.

So after updating that version, using:

brew cask install android-platform-tools

And making sure that the adb itself was pointing to the new version, the errors went away.

Upvotes: 1

Nico Lopez
Nico Lopez

Reputation: 66

Just write down platform-tools path (/Users/USER_NAME/Library/Android/sdk/platform-tools) In the .bash_profile file, located at (/Users/USER_NAME/.bash_profile), like this :

export PATH="$PATH:/Users/USER_NAME/Library/Android/sdk/platform-tools"

Upvotes: -1

JIthin
JIthin

Reputation: 1453

Address already in use means you have another instance of adb running. Check your system variable $PATH and $ANDROID_HOME and local.properties file (of your project) and your .bash_profile . Make sure that all of these has same android sdk path. Then try restarting the adb server. adb kill-server and adb start-server.

Upvotes: 12

Neha
Neha

Reputation: 27

I usually find this issue occurring when I have two instances of ADB working, i.e when I have my Eclipse and Android studio running at the same time AND when they point to different SDK Manager(platform-tools folder) on the system. Try to search for what other IDE is using ADB, kill it in the Activity Monitor and run only one instance. Or my work around was to have only one SDK Manager and point both my IDEs to one platform-tools folder.

Hope that helps.

Upvotes: 1

Jaco
Jaco

Reputation: 953

I read that you killed the adb, but as this answer says How to resolve the "ADB server didn't ACK" error? did you do that from the platform-tools folder? If your answer is yes, update the Android SDK to the lastest version via the SDK manager and update the $ANDROID_HOME

I hope it helps!

Upvotes: 2

Related Questions