Application is waiting for the debugger to attach

Question

I,m working in eclipse to develop an android app and when i tried to debugged on my samsung tab, i got the following msg on its screen "Waiting for debugger" and beneath it was written "application xxx is waiting for the debugger to attach ", I did some search and found to:

See target sdk
Restart eclipse and device
Update eclipse
Uninstall app from device and install again

I tried all this, but nothing helped. Kindly help me.

I have the same problem and it doesn´t seem to be related to the device. I tried it on my Galaxy S2 and also in the emulator, both the same. Restart doesn´t have any effect at all. I´m using android studio — Marian Klühspies, Feb 20 '14 at 16:16
I had a similar problem this moment: I always got the "Waiting for debugger" message, even when installing a signed apk of my app with detached USB. A restart of the device "fixed" the problem. — Hyndrix, Mar 08 '14 at 12:29
Possible duplicate of [How to resolve "Waiting for Debugger" message?](http://stackoverflow.com/questions/4375375/how-to-resolve-waiting-for-debugger-message) — nobody, Jan 17 '16 at 15:46

score 156 · Answer 1 · edited Jul 19 '16 at 19:20

156

In my Nexus 7 Tablet running android 4.4.2 I solved this problem by going into

Settings
Developer options
Select Debug app
was selected , Select Nothing

Done!

edited Jul 19 '16 at 19:20

Menelaos Kotsollaris

5,776
9
54
68

answered Jun 23 '14 at 04:07

silver1991

1,597
1
9
6

4

In my case on Lenovo tab I did exactly opposite. There was selected nothing, but I selected needed application. And this did the trick – Leo DroidCoder Aug 09 '16 at 09:11
This works perfectly. Except I selected the pp that i am trying to run. I don't know why the problem arose though. I am trying integration of OAuth in my application, and at first it wass not giving me trouble but then it was getting connected fine when i tried via Android Studio, but was not working when I tried opening the app from device itself. If anyone knows why this happens please let me know. I can't show you logs as I encounter this problem when device is disconnected from computer – hyperCoder Sep 30 '18 at 23:18
time saver!, thnxs – MAhipal Singh Jun 02 '23 at 14:02

score 41 · Answer 2 · answered Feb 25 '16 at 20:18

Sometimes "force to close and open again" doesn´t work, so this problem could be present when the application is currently in debug and is selected to be debugged, then from your device go to:

Settings -> Developer options -> Select app to be debugged -> Select Nothing

or when the application is supossed to being in "debug mode" but is not selected as be debugged :

Settings -> Developer options -> Select app to be debugged -> Select the application!

score 17 · Answer 3 · answered Jan 02 '14 at 21:35

17

I had same issue. Adding permission didn't help me, because Eclipse automatically enables debugging when it runs in debug mode.

Check your device setting whether "Wait for debugger" is unchecked under "Developer Options".

Also I tried closing and restarting Eclipse, and finally it worked!

I'm still figuring out what the real problem is, but hope this helps!

answered Jan 02 '14 at 21:35

Nari Kim Shin

2,459
1
25
33

I have checked that option, because the `Log` is not showing the messages in the Android Monitor, but it seems that the debugger is never attached. – JCarlosR Jul 03 '17 at 17:09

score 13 · Answer 4 · answered Apr 07 '14 at 07:40

13

Restarting Eclipse is the only solution which works every time for me.

answered Apr 07 '14 at 07:40

toto_tata

14,526
27
108
198

This works for me as well (on Android Studio). AS somehow gets confused and isn't able to see any debuggable processes on the device. Restarting AS fixes this. – Jeremy Jul 16 '15 at 05:06

score 9 · Answer 5 · answered Mar 18 '16 at 10:38

9

Go to Settings->Developer options. And then just turn off and on check box right to the Developer options title.

Also toggle USB Debugging again.

Worked for me

answered Mar 18 '16 at 10:38

vbevans94

1,500
1
16
15

Mandeep Singh · Answer 6 · 2019-12-02T12:51:40.527

4

I was having same problem with my emulator. What i did is,

Close the emulator
Open AVD manager
Wipe Data from dropdown for the required emulator in AVD Manager. May be same thing work for devices also.

edited Dec 02 '19 at 12:51

answered Dec 02 '19 at 04:08

Mandeep Singh

857
8
13

1

I had to do this AFTER having closed down the emulator for this to solve the issue. – Stephane Dec 02 '19 at 12:08

score 3 · Answer 7 · answered Oct 18 '13 at 08:36

3

This has been asked before. It is uncommon, but some devices need an extra permission(flag) to let the debugger attach!

So open your androidManifest.xml and add this permission:

<uses-permission android:name="android.permission.SET_DEBUG_APP"></uses-permission>

answered Oct 18 '13 at 08:36

bofredo

2,348
6
32
51

3

Tried it, didn't help. – Johan Dec 19 '13 at 13:53

score 2 · Answer 8 · answered Jan 16 '17 at 07:37

Another reason for this dialog to hang there is when you have breakpoints in different processes of your components (application / activity etc...).

For example:
If you have a breakpoint in an activity that runs on a different process than your main application you will see this dialog until you attach the debugger to the process manually.
For android studio it will be using the icon in the middle:

The intuitive reason for this will be that when you run in a debug mode the debugger is attached to your main application process and not to all your other processes, thus you need to specify manually to which process you want to attach your debugger.

score 1 · Answer 9 · edited May 20 '15 at 18:27

1

I had this problem when I press only F11 to Run.

Pressing F11 does debug. In order to run, press Ctrl+F11.

I haven't ever seen this problem after do like this.

edited May 20 '15 at 18:27

OhBeWise

5,350
3
32
60

answered May 20 '15 at 18:00

Hyeonjin Jung

11
2

score 1 · Answer 10 · answered Jun 09 '16 at 21:00

1

I ran into this issue on Android Studio 2.0 with a Nexus 6 running 6.0.1.

I tried most of the suggestions above and finally fixed it by restarting both Android Studio and my Nexus 6.

answered Jun 09 '16 at 21:00

josef

29
1

score 1 · Answer 11 · answered Oct 01 '18 at 14:51

1

I had this same issue and eventually found that in AndroidManifest.xml the Application element had the following attribute:

 android:debuggable="false"

I changed this to

 android:debuggable="true"

And the debugging then worked correctly.

answered Oct 01 '18 at 14:51

BruceHill

6,954
8
62
114

score 1 · Answer 12 · answered Sep 09 '21 at 21:09

I have tried the following to no avail:

Restart the Android device.
Turn Developer options off/on under the Settings of the Android device.
Disable/enable USB debugging.
Restart Android Studio.

It started working after: Android Studio > File > Invalidate Caches/Restart...

score 0 · Answer 13 · answered Sep 12 '14 at 18:53

I had the same problem with my Samsung S4 mini: after hibernating my pc with running eclipse, my phone couldn't connect with the debugger anymore. Restarting phone and eclipse didn't work.

I found, that my eclipse "disabled" the debugger in the android devices view: Window menu -> Show View -> Other -> Android -> Devices (also called DDMS view)

There was a red bug in front of my device. I enabled debugging by pushing the green bug button and now debugging works fine. This also works, if there is no bug in front of your debugging device.

score 0 · Answer 14 · answered Mar 25 '15 at 08:02

It's also good to investigate port 8700 (the DDMS "base port", a port forwarder). When TCPView shows that this port is kept by process "", it's impossible to connect to ADB and debug. This process can't be killed nor terminated in TCPView. After logging out of Windows and logging in again, this port is free again. After starting AndroidStudio/IntelliJIdea this port is owned by process "idea64.exe" and its possible to debug.

When application crashes and AndroidStudio is restarted without stopping debugger (which also detaches from ADB), it may happen that port 8700 is not released, blocked by process "".

TCPView: https://technet.microsoft.com/en-us/library/bb897437.aspx http://developer.android.com/tools/debugging/ddms.html

score 0 · Answer 15 · answered Aug 19 '15 at 14:06

0

I got this error even when the USB was unplugged, and the app wouldn't start.

The only thing that worked for me was restarting the Android device.

answered Aug 19 '15 at 14:06

live-love

48,840
22
240
204

score 0 · Answer 16 · answered Jan 17 '16 at 11:46

0

I found this simple solution to it. Just click on the debug panel tab at the lower potion of your eclipse or wherever it is. Tada!! It works! It seems eclipse is getting old it needs a slight nudge. Works every time for me!

answered Jan 17 '16 at 11:46

Utsav Gupta

3,785
5
30
52

score 0 · Answer 17 · answered Dec 12 '17 at 07:08

0

I got stuck with this when I tried to debug from IntelliJ cause I had both IntelliJ and Android Studio open. Even if there where no debug-process going on in Android Studio, I was able to launch debug from IntelliJ after I closed Android Studio.

answered Dec 12 '17 at 07:08

superodde

131
1
3

score 0 · Answer 18 · answered Oct 04 '20 at 11:16

0

Restarted the Android Studio but that didn't help. Unplugged the device from USB and plugged it back in which did the trick for me, no changes needed in Developer options in the phone settings.

answered Oct 04 '20 at 11:16

tariq101

127
2
6

score 0 · Answer 19 · answered Dec 24 '21 at 13:13

0

For me it was when two different Android Studio were launched simultaneously

answered Dec 24 '21 at 13:13

Vladimir Berezkin

3,580
4
27
33

score 0 · Answer 20 · answered Aug 26 '23 at 07:15

0

Just run ./gradlew clean and see this error are wiped out

answered Aug 26 '23 at 07:15

Chandan Payra

21
4

score -1 · Answer 21 · answered Sep 19 '13 at 12:54

-1

It's normal message when you debugging your application. Just wait for several seconds and app will start.

answered Sep 19 '13 at 12:54

Autocrab

3,474
1
15
15

9

Even i waited for 10 mnts and more..but it didn't – saadsaf Sep 19 '13 at 14:01
That's strange. It's always starts when I debug my applications, but i'm working in Intellij Idea, not in Eclipse – Autocrab Sep 19 '13 at 14:49
3

This is not the issue here... Some users have the message on screen FOREVER. – GabrielOshiro Jul 05 '16 at 19:20

Ootvia · Answer 22 · 2013-10-18T08:31:18.010

-1

Simply force to close then, open it again :)

Edited: force to close the application, and then go to menu and start the application by clicking on the apps icon

edited Oct 18 '13 at 08:31

answered Oct 16 '13 at 07:30

Ootvia

7
3

The message appears again because we are trying to debug the app. – JCarlosR Jul 03 '17 at 17:07

Application is waiting for the debugger to attach

22 Answers22

Linked