Why does Android Studio say "Waiting for a debugger" if it is NOT debugged?

Question

I am working with Android Studio. From last night, when I launched the project on my device, the message “Waiting for debugger” will appear. This is a very strange behavior because I am not debugging the application.

I tried to remove the application from my device and click "Run" in Android Studio. The message will appear again.

I tried restarting Android Studio. The message will appear again.

The only way to correctly install the application on my phone is to click "Debug". A message appears, but it closes automatically. Then the application works fine.

I tried with

<application android:debuggable="false" /> 

... and a message still appears.

LogCat says:

 E/InputDispatcher﹕ channel ~ Channel is unrecoverably broken and will be disposed! E/Launcher﹕ Error finding setting, default accessibility to not found: accessibility_enabled 

Respectfully, on the first line of the error, someone says that problems can begin after renaming a resource . But that is not my business.

Refers to the second line of the error ... I do not know. I really don't know what is happening with my IDE.

Answer 1

I ran into this problem in the past and again today. In my case, the problem is resolved by rebooting the device. After a clean boot, I can start the application again and the "Waiting for a debugger" prompt does not appear.

Answer 2

You can fix this problem without rebooting the device. Just go to “Android device” → “Settings” → “Developer options” → “Select an application for debugging” . This will probably point to your application. Just select an option and then select "No".

Note. As already mentioned, even if “No” is already selected, a repeated selection of “No” appears to fix the problem.

Just to be clear: this is on a device not in Android Studio (see a very useful comment from Regis_AG).

Answer 3

faster than rebooting. Just go into the developer options and turn it off and on again (do not forget to also check the usb debugging option), it worked for me (Neuxs5).

Answer 4

After 8 hours on this issue, I feel obligated to share this reason. My / etc / hosts was bad.

Make sure you can ping localhost and that it is defined as 127.0.0.1. AS is waiting for connection to localhost: 8600.

Answer 5

1) Clear cache cache of Android cache from file-> Invalid cache / restart.

---

2) After restarting the Android studio, restart the Android emulator.

Answer 6

I have the same problem. In my case, two development environments open simultaneously: Android Studio and Eclipse. After closing Eclipse and starting the debugging process, it works fine again. Hope this help!

Answer 7

You can check your debugging option in Dev setup on your AVD. Take a look at the following picture:

developer settings example

Answer 8

I had this problem; In Android Studio, I accidentally hit Run> Debug Application instead of Run> Run Application . I solved the problem. In my case, I had to run the application to run in DEBUG mode. Here were my steps -

1) The Android device must be able to connect to the development PC on port 8600. This connection was prohibited by my firewall configuration. I turned off the firewall. After confirmation, I created a firewall rule to allow connectivity between devices on port 8600 .

2) To check the port availability, you can go to Android Studio, Run> Attach a debugger to the Android process . This will cause the Android device application running in DEBUG mode to connect to your PC for Android Studio development.

3) After the application has started once, you can go back and Run> Run "Application" and you will no longer get the annoying screen "WAIT for DEBUGGER".

4) And you can also Run> Debug "Application" . The device will show “Waiting for a debugger” for a moment, and then Android Studio will launch the debugger console and help you remotely debug your Android device application!

Good luck.

Answer 9

I already solved this problem by rebooting my device. This is a problem with the device, not a problem for Android.

Answer 10

My computer ran little on memory, and this problem arose quite often. The fix was to free up more memory by deleting old files / applications. I notice that working emulators like Android TV usually need a lot of memory so they can predict

Answer 11

I uninstalled the application that was having this problem.

Then I installed the application in debug mode.

This solved the problem. Now it works fine.

Answer 12

I fixed this by making a duplicate Virtual Appliance after erasing an existing Virtual Appliance.