E/Art: failed sending a reply to the debugger: the solution of the broken pipe

Explanation error:

E/ART: Failed to send reply to the debugger: the pipe is broken.

What is e/art?

Art is an IME of android (This is the bytecode interpreter on Android phones. E is just the record level of error.)

What is the send reply debugger?

Debugging on Android phone is to use “ADB” (Android debugging bridge). The ADB process runs on your development computer (your laptop or PC), and the daemons run on Android devices (i.e. emulators or mobile phones).

What is a damaged pipe?

Your development machine and Android device communicate like a client-server. The damaged pipeline indicates that the communication has become invalid. For example, the client (Android device) is trying to send a reply to the server (the ADB process running on the development machine), but the server has closed the socket.

How to fix it

First, make sure your application is built correctly by performing cleanup/rebuild

Then, if you use USB to debug and run the application on a real phone, you can usually solve the problem by unplugging the USB cable and then re-inserting it to reestablish the client/server connection.

If this doesn’t work, you can disconnect the USB cable (stop the emulator if necessary) and close the Android studio. This is usually enough to stop the ADB process. Then, when you open Android studio again, it will restart and reestablish the connection.

If this doesn’t work, you can try using the instructions to manually stop the ADB server in this issue. For example, you can try to open a command prompt or terminal, and then go to the SDK /platform-tools directory and enter:
the

adb kill-server
adb start-server

* daemon not running; starting now at tcp:5037
* daemon started successfully

When this appears, It’s done