In the application directory, run the startup script launching the repository manager: Linux or Mac. Go to the application directory which contains the repository manager file you need to start up.

The ADB log is telling: 8568-8568/it.myapp:myprocess W/ActivityThread﹕ Application it.myapp is waiting for the debugger on port 8100.Ĩ568-8568/it.myapp:myprocess I/System.out﹕ Sending WAIT chunkĪlso, I can't find an easy way to disconnect nor reset ADB connection in Android Studio. nexus-) and data directory (i.e./sonatype-work/nexus3) are created after extraction.

Even re-installing the app doesn't solve. Update: Opened a bounty since this issue is so annoying. I can't be the only one encountering this issue :-/ Update: The same thing happens when debugging on Nexus 7 (2013) running Android 5.0 and testing on another machine rendered the same result. So the question is what can I do to make Android Studio debugging work? And on the same computer I can perform debugging using Eclipse on the same device without any issues. VORTEX - Beginner's Guide 1 (of 4) video tutorial series by Gopher. This has being the case from Android Studio 0.8.8 all the way to 1.0. The new 'official' Nexus site mod manager. While the device (Samsung Galaxy S3 Android 4.3) I'm debugging would display Whenever I try to use Android Studio's Debug function, the Run status would always stuck at: Launching application: /.ĭEVICE SHELL COMMAND: am start -n '/' -a -c

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.

Nexus mod manager custom launch command