reactive run-android failed "could not install *smartsocket* listener: Address already in use"
See original GitHub issue:app:assembleDebug UP-TO-DATE
:app:installDebug
05:53:18 E/adb: error: could not install *smartsocket* listener: Address already in use
05:53:18 E/adb: ADB server didn't ACK
05:53:18 E/adb: * failed to start daemon *
05:53:18 E/adb: error: cannot connect to daemon
05:53:18 E/ddms: '/Users/bjhl/Library/Android/sdk/platform-tools/adb,start-server' failed -- run manually if necessary
:app:installDebug FAILED
the simulator i used is genymotion
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:29
Top Results From Across the Web
could not install smartsocket listener: Address already in use
This article is about error message: “error: could not install smartsocket listener: Address already in use”.
Read more >Android - could not install *smartsocket* listener - Stack Overflow
When I try run my Android application I get this exception: Error while waiting for device: java.
Read more >reactive run-android failed "could not install ... - Desarrollolibre
reactive run-android failed "could not install *smartsocket* listener: Address already in use" en MacOS. 22-09-2021 - Andrés Cruz.
Read more >Expo ADB server didn't ack error. So I was ... - Ricky H. Putra
error : could not install *smartsocket* listener: Address already in use. ADB server didn't ACK * failed to start daemon *
Read more >syumai on Twitter: "Genymotion上のAndroidでExpo動かそうと ...
reactive run-android failed "could not install *smartsocket* listener: Address already in use" ·... :app:assembleDebug UP-TO-DATE :app:installDebug 05:53:18 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
the adb version on your system is different from the adb version on the android sdk platform-tools link it works for me
1 check sys adb version
2 check sdk adb version
3 copy
that’s all
I had the same issue and just did
Got another adb process already running but not sure why it was started
Just did a kill -9 11809 and started adb server and its working fine now