1

I am running my android appium execution on MAC machine.

I have installed android studio and have set the path variable.

While executing adb start-server I got below error:

adb server version (32) doesn't match this client (36); killing...

error: could not install smartsocket listener: Address already in use

ADB server didn't ACK

failed to start daemon

error: cannot connect to daemon

Firewall setting is turned OFF and no other ADB present like GenyMotion.

Community
  • 1
  • 1
RISHI KHANNA
  • 354
  • 5
  • 23
  • if the server doesn´t ACK on your MAC it seems to be a LACK and you should look at this FACT (boww, bum bum bum, booww): http://stackoverflow.com/questions/35959350/react-native-android-genymotion-adb-server-didnt-ack – Opiatefuchs Jun 22 '16 at 10:16
  • I am not using Genymotion. Only Android-studio – RISHI KHANNA Jun 22 '16 at 10:17
  • ok, that was in my case some time ago. So, do you see the adb.exe in your task manager? – Opiatefuchs Jun 22 '16 at 10:22
  • No, nothing in my Activity Monitor also – RISHI KHANNA Jun 22 '16 at 10:27
  • I am not sure but try to kill the adb server in your sdk directory with for example: `C:\sdk\platform-tools>adb kill-server` (depends on your path) and restart it via `C:\sdk\platform-tools>adb start-server` .....does this work? – Opiatefuchs Jun 22 '16 at 10:38
  • otherwise, maybe the setting of your path variable is not correct. If it doesn´t work, please post the path variable... – Opiatefuchs Jun 22 '16 at 10:40
  • No it didn't worked.. I tried "adb version" and it listed the version correctly: "Android Debug Bridge version 1.0.36" – RISHI KHANNA Jun 22 '16 at 11:39
  • For "adb devices" it displayed the same error: List of devices attached adb server version (32) doesn't match this client (36); killing... error: could not install *smartsocket* listener: Address already in use ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon – RISHI KHANNA Jun 22 '16 at 11:39
  • then the only thing I can imagine is that adb is not up to date. Open the sdk manager and be sure everything is with the latest version... – Opiatefuchs Jun 22 '16 at 11:43
  • Today again I have re-installed everything...so its new version only – RISHI KHANNA Jun 22 '16 at 11:48
  • Let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/115300/discussion-between-rishi-khanna-and-opiatefuchs). – RISHI KHANNA Jun 22 '16 at 12:04

1 Answers1

0

Did you set android sdks, platform-tools and tools path in your bash_profiles? Or Could you navigate to android sdks path and try to execute adb start-server command? If you are running appium from appium app then I would recommend to set android sdks path in settings.

Suman
  • 436
  • 4
  • 10
  • This is what my bash file holds for android home: export PATH=/Users/Admin/Library/Android/sdk/platform-tools:$PATH export PATH=$PATH:~/.android-sdk-macosx/platform-tools/ – RISHI KHANNA Jun 22 '16 at 12:03
  • Are you using 2 different android sdks? Root path for platform-tools and tools should be same. export ANDROID_HOME=/Users/Admin/Library/Android/sdk export PATH=$PATH:/Users/Admin/Library/Android/sdk/platform-tools export PATH=$PATH:/Users/Admin/Library/Android/sdk/tools I think because of different platform-tools bash is getting confused. I recommend to use one path only. Also, if using appium app, set android sdks path in settings. – Suman Jun 22 '16 at 12:08
  • Yes did that.. still same issue – RISHI KHANNA Jun 22 '16 at 12:25
  • If you navigate to your add location (/Users/Admin/Library/Android/sdk/platform-tools) and execute the ads start-server command, do you still get error? – Suman Jun 22 '16 at 12:29
  • I tried starting adb in different port using: adb -P 8345 start-server and server successfully started in this port but "adb devices" is returning empty list of devices – RISHI KHANNA Jun 22 '16 at 12:38
  • http://stackoverflow.com/questions/23415746/how-to-resolve-the-adb-server-didnt-ack-error – Suman Jun 22 '16 at 13:02