ChatGPT解决这个技术问题 Extra ChatGPT

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

https://i.stack.imgur.com/vtvHm.png

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.

If you haven't already, you could try unchecking "Use Host GPU" in the AVD Config for your emulator.
@JosephWebber Thanks for the suggestion, but I'm debugging on an actual hardware though
are you using a custom mod or stock one?
I tested on Nexus 7 2013 with stock Android 4.4.2, and Samsung S3 with Android 4.3, neither worked.
Hi, I got similar issue, I have try solution here but not work. Please help answer my question: stackoverflow.com/q/40838494/5241603

T
Top-Master

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

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

OR

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?


where this command should be used? in the terminal?
@AndreaBuzzelli Yes, in your terminal
Thanks man. Just ran this in Terminal in AS and it cleared it up for me.
O
Ohad Cohen

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)


Mine seemed to connect to the app before it was completely launched and "waiting for debugger", telling it to connect a second time after it was already connected resolved that. (android studio 162)
I was just in the Release mode :D
N
Nisar Ahmad

Restarting Testing device fix the issue for me.


Same here, I tried everything above and this one did it for me.. Sigh
Same here. My device was showing the message even when not connected to dev machine (not connected over adb in any way). So all the advice regarding Android Studio and ADB were irrelevant. TurningUSB debugging off/on didn't help either Rebooting the device was the only way to fix it.
Me device (emulated) was showing that message any time I opened the app (through Android Studio, or just from the launcher). Tried a whole bunch of stuff. Full on rebooting the phone didn't occur to me because it's been closed several times (but with a saved state, duh). This did the trick!
yes, holy restart helped for me too.
h
hris.to

Restarting Android Studio fix the issue for me.


Funny thing is that is the usual fix for Xcode problems. Apparently both platforms are not that different at the end :)
No. Not for me.
Sorry to hear that. Apparently 2 years later, there is another problem & (hopefully) solution :)
R
Rohit Kumar

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.

https://i.stack.imgur.com/pUQAl.png

Updated Image for Attach Debugger to Android process Icon

https://i.stack.imgur.com/qn4Vh.png


what if i am not launching debug, bug just running the app
Exactly lxknvlk, here it is 2021 using android studio 4.2.2 and this major pain keeps showing up. Funny thing is it just all of a sudden starts doing this and NONE of the solutions does anything to fix it. I am using Nexus 5X API 28x86 and now I've wasted hours already trying to fix it. Restarted everything including rebooting the computer.
what if there are no processes listed?
@jave.web it is the solution for waiting state for the process.
@RohitKumar I know but I only see devices in the attach debugger, but no processes to select :/
u
user2658370

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.


Fudge, this worked for me when other answers did not work (restarting, deleting ".idea", etc). This answer is more than 5-years old and I am using the latest version of AS at the end of 2021. Why haven't Google fixed this issue? Even if they could not figured out the root cause, they could have easily make AS ignore that setting and install the APK if debugging keeps failing (unresponsive) for a certain amount of time....
N
Narshim

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.


One thing to add: Maybe your have to restart android studio after closing the open instanc(es)... This helped me!
Another improvement - it does happen if you have just another IntelliJ IDEA open. Not need to be android studio
Android Studio was unable to start debugging in an Android Emulator, and closing IntelliJ solved the problem. The project opened in IntelliJ was not even an Android project (but just a console Kotlin project). Maybe it is because the Android component is installed in IntelliJ.
C
Community

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


This solved the problem. Suddenly I couldn't debug on real hardware or the emulator. Rebooting everything didn't work. I could get by using Run -> Attach debugger to Android process, but it gets annoying after a while. It started happening after upgrading gradle, as the IDE suggested.
FYI ticket in google issue tracker: issuetracker.google.com/issues/37117600
standard answer to all android studio issues, reboot :). windws os in the making..
Didn't help. The message persists.
Thank you vman! I was sweating bullets. Not being able to debug is a disaster for me and this solved it.
J
John Ruban Singh

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


thanks you save my day its working fine.
K
Kai

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).


I have the same problem, very annoying since requires phone reboot. Using JDK 1.7.0b147
JDK 8 is not officially supported by Android Studio - I have had problems compiling projects and they were resolved by going back to JDK 7.
where to change the version of JDK8 to JDK7 in latest version of Android Studio
@AnandKrish you have to change the default JDK/JRE of the computing environment, basically when you execute javac -version, the result should be javac 1.7.xxx. On the other hand, I'm using JDK 8 (1.8.0_60) on OSX and the aforementioned issue doesn't seem to exist anymore.
Correct! My machine have JDK 7 and JDK 8 installed. I have resolved this issue by change JDK location (Android Studio 2.1.1: File - Project Structure - SDK Location - JDK location) from JDK 8 to JDK 7.
J
Jeff T.

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


M
MyFoenix

https://i.stack.imgur.com/q2eWg.png


E
Eduardo Boada

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


Too annoying. This just started happening today after YEARS of successful debugging with no problems.
I solved it by factory restoring my device. I need to get rid of it the as soon as possible.
B
Billy

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


R
Ram Chhabra

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


Only answer that worked for me. Probably the right answer for people facing our version of the issue.
F
Fasiha

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.


R
RAHUL JOSHI

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.


d
diogo

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.


V
Vicky

Android studio 3.0 and Above

Disable the instant Run

https://i.stack.imgur.com/VhHHk.png


With Android Studio 3.5.x, this option becomes HotSwap.
s
solamour

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".


This is also true when running IntelliJ Idea. You can't even attach the debugger.
A
Ali Hussein Al-Issa

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.

https://i.stack.imgur.com/BCCIV.png


X
Xinoon

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


F
Fran Marzoa

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.


As a side note, beware with USB hubs and low quality USB cables. I've experienced this sort of problem due these too.
A
Alexey

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


Thank you, this is the only thing that fixed my issue, which started happening after including exoplayer locally in my project.
k
kudzai zishumba

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

press enter

and again adb start-server

press enter


J
Juan Saravia

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.


G
Gk Mohammad Emon

Make sure that your Active Build Variant is debug.

https://i.stack.imgur.com/Gb3Ol.png

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*/
        }
    }

Y
Yusuf X

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.


I
Igor

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)


G
Gianluigi Liguori

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