'Debugging with Android Studio stuck at "Waiting For Debugger" forever

UPDATE The supposed duplicate is a question on being stucking in "Waiting For Debugger" when executing Run, while this question is on being stucking in "Waiting For Debugger" when executing Debug, the steps to produce the problem is different, and the solution(s) are different as well.

Whenever I try to use Android Studio's Debug function, the Run status would always stuck at:

Launching application: com.astrotek.parashoot.debug/com.astrotek.ptpviewer.StarterActivity.
DEVICE SHELL COMMAND: am start -n "com.astrotek.parashoot.debug/com.astrotek.ptpviewer.StarterActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.astrotek.parashoot.debug/com.astrotek.ptpviewer.StarterActivity }

While the device (Samsung Galaxy S3 Android 4.3) I'm debugging would display

enter image description here

This has being the case from Android Studio 0.8.8 all the way to 1.0. And on the same computer I can perform debugging using Eclipse on the same device without any issues.

So the question is what can I do to make Android Studio debugging work?

Update: The same thing happens when debugging on Nexus 7 (2013) running Android 5.0; and testing on another machine rendered the same result. I can't be the only one encountering this issue :-/

Update: Opened a bounty since this issue is so annoying. Even re-installing the app doesn't solve. Nexus 5 running Cyano, Win7 64. The ADB log is telling:

8568-8568/it.myapp:myprocess W/ActivityThread﹕ Application it.myapp is waiting for the debugger on port 8100...
8568-8568/it.myapp:myprocess I/System.out﹕ Sending WAIT chunk

Also, I can't find an easy way to disconnect nor reset ADB connection in Android Studio.

Solution 1:^[1]

Both of my dev machines have JDK 8 installed, the debugging function is restored once JDK 7.0.71 was installed and JAVA_HOME environmental variable was set to point to the new JDK.

Guess there's some compatibility issue between Android Studio + ADB + JDK8 (Eclipse + ADB + JDK8 works fine).

Solution 2:^[2]

Obviously is yet another Android Studio, or rather ADB bug.

Just use this command to disable it. adb shell am clear-debug-app

Ensure there is nothing to wait for, by automatic uninstall from Device before each test-run, using Gradle's uninstallAll task, as mentioned in:
stackoverflow.com/Auto uninstall before install?

Solution 3:^[3]

On some machines/projects the debugger do not attach automatically so you need to attach it manually (studio menu -> Run -> Attach debugger to Android process)

Solution 4:^[4]

Restarting Testing device fix the issue for me.

Solution 5:^[5]

Restarting Android Studio fix the issue for me.

Solution 6:^[6]

After clicking on the run icon. If it is stuck waiting for a debugger means it is not attached to the app. You have to manually attach by clicking on Attach Debugger to Android process. It is on the right side of the run icon. I had focus this icon in linked image.

Updated Image for Attach Debugger to Android process Icon

Solution 7:^[7]

Debugger stopped connecting for me today and nothing worked until I tried the following:

Go to Run, Edit-Configurations, Miscellaneous Tab, uncheck 'skip installation if APK has not changed' Apply, OK.

Debugger started to connect again.

Solution 8:^[8]

This problem occurs when you open more than one instance of Android studio, so you need to attach the debugger manually like mentioned above.

You may need to close other instances of Android studio.

Solution 9:^[9]

A similar question has been asked recently and the solution may work for some and is very quick.

Clearing the Intellij IDEA (Android Studio) .idea directory which contains configuration information worked for me:

Exit Android Studio

Navigate to the project you are trying to debug

Backup any files inside .idea that you modified (if your project checks any of these into VCS)

Delete .idea directory

Open the project in Android Studio

Solution 10:^[10]

I faced this problem in android studio 3.0. Just restarted device solved.

Solution 11:^[11]

I tried the top three rated answers but failed. After rebooting my mobile, the problem is solved. No more long "Waiting for Debugger".

Solution 12:^[12]

I just managed this problem, after several days of trying the above solutions. So I closed the emulator, run AVD manager and in device menu choose - "wipe data" So in next run I was free from stucked debugger.

Solution 13:^[13]

When the Device displays the message go to Run->Attach debbuger, then select a debbuger. it'll start the activity.

Solution 14:^[14]

This fixed it for me. Android Studio -> File -> Invalidate Caches & Restart...

Solution 15:^[15]

I had the same problem. Restart my android phone device worked for me.

Solution 16:^[16]

This solution works for me:

turning off the USB debugging from my device settings , and then turning it on again.

its Much quicker and easier than restart the device.

Solution 17:^[17]

How it worked for me.

1 Start Android Device Monitor from Tools -> Android -> Android Device Monitor

2 Click on Stop for the process you are facing the issue from list of devices.

Solution 18:^[18]

Most of the times this is caused because of the overload of resources and threads over the emulator. Or even for the lock of objects that GC couldn't set free: http://developer.android.com/intl/pt-br/tools/debugging/index.html

Usually, a single restart of it will solve the issue, but sometimes it asks for the IDE restart, so be sure to make both tests.

Another good test is trying to start the app in "Start mode" and then try the debug mode again...

P.S: Don't forget to kill each debug process in the IDE after each test. This will prevent your env to be more overloaded.

Solution 19:^[19]

Android studio 3.0 and Above

Disable the instant Run

Solution 20:^[20]

As for my case, running Android Studio Canary (preview release) along with the stable version was the problem. Running multiple instances of the same Android Studio flavor was OK, but mixing them often resulted in "Waiting For Debugger".

Solution 21:^[21]

For me, the issue was: The Regional Format of Windows was ARABIC. I simply changed the regional format to English (United States) and the error has fixed.

Steps to fix:

Go to Start -> type Region -> click on Region to open Region window -> from the Format dropdown, select English (United Stated) -> Click OK.
Restart Android Studio.

Solution 22:^[22]

I had the same problem. Restart my android device and closed the adb.exe process. With that I could solve the problem

Solution 23:^[23]

Well, I guess there is a plethora of circumstances that can trigger this issue. I'm using IntelliJ Idea instead, but it's mostly the same than Android Studio. My solution for this problem:

Fastest way:

Right click on the class file that contains the main activity of your project, and then on "Debug 'WhateverActivity'". This will create a new run configuration that should debug fine.

Other solution, without creating a new run configuration:

Open Run/Debug configurations and within "Android app" pick the configuration you're using to debug your app.

Locate "Launch Options/Launch" there and set it to "Specified Activity" instead of "Default Activity".

In the "Launch" field just below the aforementioned option, click on the three ellipsis (three dots) button and select your main activity.

At least it worked for me. I hope it works for others too.

Solution 24:^[24]

Got it fixed according this solution: https://youtrack.jetbrains.com/issue/IDEA-166153
I opened <project dir>/.idea/workspace.xml replaced all the
<option name="DEBUGGER_TYPE" value="Auto" /> occurrences to
<option name="DEBUGGER_TYPE" value="Java" />
and restarted Android Studio

Solution 25:^[25]

Open Command prompt and go to android sdk>platform-tools> adb kill-server

press enter

and again adb start-server

press enter

Solution 26:^[26]

Make sure that your Active Build Variant is debug.

If you also want to make your release variant APK debuggable then make a simple change in app level build.gradle -

buildTypes {
        release {
            debuggable true
            /*Your rest code*/
        }
    }

Solution 27:^[27]

Restarting everything didn't work for me. What DID work was waiting for a few minutes while Android Studio unclogged itself. This was the first time I ran the debugger; after that, Android Studio fired up the debugger quickly.

Solution 28:^[28]

For me Run->Attach debugger to Android process was working, but I had to do it every time app was launched.

Fix: There may be a problem with your 'App launch configuration'(To verify this create new project to see if it's working fine). Just delete app configuration, open MainActivity file and Run->Debug (new conffiguration will be created)

Solution 29:^[29]

Sometime it's due to the fact that in the build.gradle configuration you have to set the node:

  debug {
            debuggable true
        }

Change it back to false when you have to prepare the signed apk.

Regards

Solution 30:^[30]

Non of this solutions worked for me.

In my case was that I was debugging an App from Intellij IDEA and at the same time with Android Studio. By just closing the Intellij IDEA and removing the app I was debugging just fixed my problem.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1
Solution 2	Top-Master
Solution 3
Solution 4
Solution 5	hris.to
Solution 6
Solution 7	user2658370
Solution 8	Narshim
Solution 9	Community
Solution 10	John Ruban Singh
Solution 11	Jeff T.
Solution 12	MyFoenix
Solution 13
Solution 14	Billy
Solution 15	Ram Chhabra
Solution 16	Fasiha
Solution 17	RAHUL JOSHI
Solution 18	diogo
Solution 19	Vicky
Solution 20	solamour
Solution 21
Solution 22	Xinoon
Solution 23	Fran Marzoa
Solution 24	Alexey
Solution 25	kudzai zishumba
Solution 26	Gk Mohammad Emon
Solution 27	Yusuf X
Solution 28	Igor
Solution 29	Gianluigi Liguori
Solution 30	Juan Saravia

'Debugging with Android Studio stuck at "Waiting For Debugger" forever

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]

Solution 10:[10]

Solution 11:[11]

Solution 12:[12]

Solution 13:[13]

Solution 14:[14]

Solution 15:[15]

Solution 16:[16]

Solution 17:[17]

Solution 18:[18]

Solution 19:[19]

Solution 20:[20]

Solution 21:[21]

Solution 22:[22]

Solution 23:[23]

Solution 24:[24]

Solution 25:[25]

Solution 26:[26]

Solution 27:[27]

Solution 28:[28]

Solution 29:[29]

Solution 30:[30]