Not Able To Debug App In Android Studio

Question

I am making an app in Android Studio, now trying to debug it through adb. When I click on the word Android and the logo on the bottom bar, logcat comes up and recognizes my device. Then I see this:

screenshot

What do I need to do to my app to make it "debuggable"?

FYI was developing this app in Eclipse before and adb worked fine.

Uninstalling app from device and run it again from Android studio solved my problem — Ahmad Behzadi, Sep 27 '16 at 10:33
I had a problem today, breakpoints cannot stop the program. And It was because of setting in build.gradle. I set debug build type with minifyEnabled is true, remove this and breakpoint worked. — castle bai, Nov 16 '16 at 07:51
have a look at my answer [here](https://stackoverflow.com/questions/20537845/why-android-studio-says-waiting-for-debugger-if-am-not-debugging/51301773#51301773). that might solve the problem — Muahmmad Tayyib, Jul 12 '18 at 09:25

score 115 · Answer 1 · edited Mar 13 '18 at 21:28

115

I solved this issue after doing the following steps:

Go to Tools==>android==>Disable ADB integration and enable it again.

After that, unplug USB from device and plug in again.

Finally press shift + F9

edited Mar 13 '18 at 21:28

live-love

48,840
22
240
204

answered Dec 28 '14 at 14:46

Prathamesh Gujar

1,299
2
10
9

This is what helped me. Suddenly the debug stopped working, after this worked again. – Rui Santos Jul 15 '15 at 14:43
Stil working as of today, tried restarting and everything. – Mathijs Segers Jul 27 '15 at 08:03
1

I just needed to close and reopen android studio for that project instance to make the bug work :/ – Rachael Oct 01 '15 at 18:45
Yesterday, while nothing else helped, a reboot did the trick. – Harmen Nov 28 '15 at 14:26
This work for me. Even adb kill-server and adb start-server commands did not,but it does – Mahendra Chhimwal Jul 18 '16 at 05:54
Note for the last part: Shift + F9 is the shortcut to run Debug on Windows. On Mac, it is Control + D. – clever_trevor Jun 29 '17 at 22:09
Disable and re- Enable ADB Integration helped me on Android Studio 3.0.1 – jonathan3087 Feb 09 '18 at 14:56
30

There is no such menu item called "Tools==>android" in Android Studio version 3.1.3 and I cannot find this option anywhere – James Watkins Jul 07 '18 at 18:55
In android 3.X I posted an answer that [worked for me](https://stackoverflow.com/a/53519263/2829540) – Kevin Amiranoff Nov 28 '18 at 12:16
1

No "adb" options anywhere in the menus for Android Studio 4 – spartygw Jun 09 '20 at 21:17
5

Use this option to restart ADB in Android Studio 4: Tools -> "Troubleshoot Device Connection" Here tap "Next" button. Finally ADB restart option is there in the 4th step – Pratheesh Jan 11 '21 at 07:10

score 90 · Accepted Answer · edited Oct 27 '15 at 23:08

90

There is a Debug icon on the toolbar. It looks like a little "bug" and is located right next to the Run icon (which looks like a play button). Try launching the application with that.

Edit: The following is deprecated when using Android Studio with Gradle.

There is also a debug flag in the AndroidManifest.xml file. It is located under the application tag, and should be set to "true", as follows:

<application android:debuggable="true">
</application>

edited Oct 27 '15 at 23:08

Gabriel

3,564
1
27
49

answered May 25 '13 at 23:29

free3dom

18,729
7
52
51

1

Can we step one line at a time, just like in eclipse ? if can, how to do that ? – Ari R. Fikri Jul 30 '13 at 04:54
1

Sure you can. Once you hit a breakpoint the debug window is displayed, the toolbar at the top contains the various step commands. You can also configure the various debug keyboard shortcuts from `File` -> `Settings` -> `Keymap` - they are located under `Main menu` -> `Run`. See [this](http://www.jetbrains.com/idea/webhelp/stepping-through-the-program.html) for more info. – free3dom Jul 30 '13 at 07:37
7

The latest version of android studio doesn't mandate you to set the android:debuggable, infact it shows an squiggle which suggests to set it in the configuration rather than in the manifest. This helps in avoiding accidently publishing an app with debug information. – Soundararajan Jan 04 '15 at 06:41
Thanks @Soundararajan for bringing that to my attention. I will update the answer to reflect that. – free3dom Jan 04 '15 at 14:02
3

Not work 2015, build.gradle put buildTypes { debug { debuggable true – Sep 10 '15 at 14:48
@delive Is right. I couldn't use my breakpoints until I added that to my build.gradle. – Daniel Wood Nov 24 '15 at 20:29
Using the debug app button as suggested solved the problem. – nibbana Jul 15 '19 at 16:35
2

it is work for my. I put the in the manifest and debug perfect. Thanks – Andy Romero Jul 28 '19 at 03:26
That debug button is disabled/greyed. How do you get it to be clickable? – Pete Alvin Oct 28 '19 at 14:12
Avoid hardcoding the debug mode; leaving it out allows debug and release builds to automatically assign one – dicarlomagnus Oct 14 '21 at 19:21

score 42 · Answer 3 · answered Oct 29 '14 at 23:52

42

Another thing to be careful of (I did this so I know, duh). Be sure not to enable Proguard for debug!

answered Oct 29 '14 at 23:52

John Smith

3,493
3
25
52

6

thanks and had to make minifyEnabled false and shrinkResources false – Janardhan R Oct 25 '17 at 12:50
where to find this ?? – MartianMartian Oct 17 '22 at 15:51

score 24 · Answer 4 · answered Sep 17 '14 at 09:02

24

This worked for me:

Close Android Studio.
Open the shell, and write:

adb kill-server

adb start-server

answered Sep 17 '14 at 09:02

limlim

3,115
2
34
46

Just what I was looking for. Previously, I could get this done with a simple `adb reconnect` command, but it doesn't do this anymore in AS 3.1 (maybe I'm doing something wrong, or not enough? – VictorB May 14 '18 at 06:54
Btw, this solution worked for me without closing AS, or the terminal session. – VictorB May 14 '18 at 06:56

score 23 · Answer 5 · answered Feb 17 '16 at 10:30

23

    <application android:debuggable="true">
</application>

This no longer works! No need to use debuggable="true" in manifest.

Instead, you should set the Build Variants to "debug"

In Android Studio, go to BUILD -> Select Build Variant

Now try debugging. Thanks

answered Feb 17 '16 at 10:30

itzo

1,220
14
18

The Build menu doesn't have a "Select Build Variant" option. – Pete Alvin Oct 28 '19 at 12:49

score 21 · Answer 6 · answered Aug 01 '13 at 18:25

21

I also randomly had this problem even after debugging many times in Android Studio. One day the debugger just wouldn't attach. I just had to quit Android Studio and reopen it and the debugger started working again.

answered Aug 01 '13 at 18:25

Adam Johns

35,397
25
123
176

score 13 · Answer 7 · answered Apr 26 '15 at 09:42

13

If your Application used to be debuggable, and suddenly it's no more debuggable.Here is my solution

disable and enable USB debug switch in your phone.
Uninstall your application.
click Run in Android Studio.

answered Apr 26 '15 at 09:42

Miao1007

944
6
22

and check "wait for debugger" 2022.10.17. Mac M1 Dolphin – MartianMartian Oct 17 '22 at 15:59

score 11 · Answer 8 · answered Dec 17 '14 at 09:41

11

Make sure you have enabled the ADB integration.

In Menu: Tools -> Android -> Enable ADB integration (v1.0)

answered Dec 17 '14 at 09:41

myfknoll

455
5
15

score 8 · Answer 9 · answered Aug 01 '13 at 09:18

8

One case where you can be unable to debug an application in Android Studio is when you have the "release" build variant selected. Happened to me - Gradle builds a release version of the app (which is not debuggable) and then Android Studio fails at trying to connect the debugger.

answered Aug 01 '13 at 09:18

Harri

828
10
13

1

This has tripped me up a number of times, even in other IDEs. I believe the ability to debug release is configurable in most IDEs and sometimes advised if you want to attach the debugger to released apps. – visc Sep 12 '17 at 16:57

score 8 · Answer 10 · answered Jun 24 '14 at 17:35

This occasionally happens to me and I have yet to figure out why. None of the already posted solutions have worked for me. The only thing that works for me is to:

Uninstall application from device.
Clean Project. "Build -> Clean Project."
Rebuild and install.

score 8 · Answer 11 · answered May 25 '16 at 13:20

8

"Attach debugger to Android process" icon shoud be used in case when you set custom "android:process" in your Manifest file.
In my case I should select suitable process and click OK button just after "Wait for debugger" dialog appears.

answered May 25 '16 at 13:20

user1700099

466
5
6

horrible workaround but the only thing working for me right now, THANKS!!! – Jules Apr 18 '17 at 07:45
Worked for me even though I did not have a custom "android:process" in my Manifest file. – Jason Bowers Aug 06 '17 at 15:47
this was the solution for me. Thanks – gmartinsnull Oct 29 '18 at 21:41

CoolMind · Answer 12 · 2018-02-28T07:33:10.270

In my case near any line a red circle appeared with a cross and red line with a message: "No executable code found at line ..." like in Android studio gradle breakpoint No executable code found at line.

A problem appeared after updating of build.gradle. We included Kotlin support, so a number of methods exceeded 64K. Problem lines:

buildTypes {
    debug {
        minifyEnabled true

Change them to:

buildTypes {
    debug {
        minifyEnabled false
        debuggable true

Then sync a gradle with a button "Sync Project with Gradle Files". If after restarting of your application you will get an error: "Error:The number of method references in a .dex file cannot exceed 64K. Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html", then, like in The number of method references in a .dex file cannot exceed 64k API 17 add the following lines to build.gradle:

android {

    defaultConfig {
        ...

        // Enabling multidex support.
        multiDexEnabled true
    }
    ...
}

dependencies {
    implementation 'com.android.support:multidex:1.0.2'
}

UPDATE

According to https://developer.android.com/studio/build/multidex.html do the following to enable multidex support below Android 5.0. Else it won't start in these devices.

Open AndroidManifest and find tag <application>. Near android:name= is a reference to an Application class. Open this class. Extend Application class with MultiDexApplication so:

public class MyApplication extends MultiDexApplication { ... }

If no Application class set, write so:

<application
        android:name="android.support.multidex.MultiDexApplication" >
    ...
</application>

score 6 · Answer 13 · answered Sep 01 '20 at 20:04

6

In my case, i forgot minifyEnabled=true and shrinkResources=true in my debug buildType. I change these values to false, it's worked again!

answered Sep 01 '20 at 20:04

Mete

2,805
1
28
38

score 4 · Answer 14 · answered Dec 08 '15 at 10:13

4

Check, if you're app-project is selected in the drop-down menu next to the debug-button. Sometimes Android Studio just resets this selection...

answered Dec 08 '15 at 10:13

longi

11,104
10
55
89

score 4 · Answer 15 · answered Feb 05 '16 at 18:03

If you enable

<application android:debuggable="true">
</application>

In the application manifest.xml make sure you disable it when generating the final signed apk since this can serve as a security loop hole for attackers. Only use it if only one of your applications does not show the logs. However before considering that option try this:

Navigate to tools in the android studio

 Tools==>android==>disable adb integration and again enable it

score 4 · Answer 16 · answered Mar 22 '20 at 22:42

4

Restart the adb server, from android studio: Tools -> "Troubleshhot Device Connection"

answered Mar 22 '20 at 22:42

Webdma

714
6
16

score 4 · Answer 17 · answered Sep 26 '20 at 06:22

4

This worked for me in Android Studio 3.6.3

Settings -> Build, Execution, Deployment -> Debugger -> Android Debug Bridge -> Enable 'Use libs backend'

answered Sep 26 '20 at 06:22

Pavel Kataykin

1,527
15
14

score 3 · Answer 18 · answered Jun 16 '15 at 15:31

3

Also make sure you're not using other applications that might be using ADB too, like Eclipse for example.

answered Jun 16 '15 at 15:31

Pedro Oliveira

20,442
8
55
82

score 3 · Answer 19 · answered Jun 13 '17 at 07:38

3

I tested all ways and non of them worked !!!

finally had to change the adb port and it worked. first kill adb server like below:

adb kill-server

then restart it using another port

adb -P 5038 start-server

answered Jun 13 '17 at 07:38

Amir Ziarati

14,248
11
47
52

score 3 · Answer 20 · answered Mar 28 '18 at 07:08

In my case, Had to remove the proguard in debug Build Type by completely clearing the text file proguard-rules.pro and making minifyEnabled false in build.gradle file

  debug {
            debuggable true
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }

score 2 · Answer 21 · answered Apr 21 '16 at 16:02

2

Be sure to enable developer mode and USB debugging on the device or emulator. (Easy to forget when setting up a new one.)

answered Apr 21 '16 at 16:02

Ken Root

21
3

score 2 · Answer 22 · answered May 23 '16 at 09:05

2

You also should have Tools->Android->Enable ADB Integration active.

answered May 23 '16 at 09:05

NSK

251
3
10

score 2 · Answer 23 · answered Jun 20 '17 at 15:08

2

I did clean build using below command.. Surprisingly worked.

sh gradlew clean build

Hopefully someone get help!

answered Jun 20 '17 at 15:08

shaiban

331
5
12

1

In which console we have to start it? – NoWar Feb 01 '18 at 01:34
Run this command in the android studio terminal or navigate to your project from external terminal – Haider Ali May 08 '19 at 11:01

score 2 · Answer 24 · answered Jan 07 '20 at 12:47

2

I was able to fix it by going to Run -> Edit Configurations, selecting my project, selecting the Debugger tab, then changing 'Debug type' from 'Auto' to 'Dual':

answered Jan 07 '20 at 12:47

Bajrang Hudda

3,028
1
36
63

score 2 · Answer 25 · answered Jul 08 '20 at 02:12

In my case, I was trying to debug from a QA build. Change the build variant to Debug and it should work.

To change the build variant, click the menu on the left bottom named "Build Variants"

In case this menu is not available in your IDE you can do the following.

Double click your shift button and you should see a search window popping.
Type "Build Variants" as shown below

3. Now change your build to debug from QA or Release.

score 2 · Answer 26 · answered Apr 04 '22 at 07:56

April 2022 :

all the answers did not help me in android studio 2022, I found my solution, maybe help someone else: I got this error in debug window when I was using breakpoint and debug mode:

Signal: SIGILL (signal SIGILL: illegal instruction) android studio

So the solution is:

go to Run> Edit Configuration > Debugger Tab select Java only from debug type.

score 1 · Answer 27 · answered Sep 27 '16 at 10:32

1

This solved my problem. Uninstall app from device and run it again via Android studio.

answered Sep 27 '16 at 10:32

Ahmad Behzadi

1,006
15
30

score 1 · Answer 28 · answered Mar 17 '18 at 22:36

1

For me, it happened when I used Proguard, so by trying all the solutions I cleaned my project and pressed the debug button on Android Studio and it started debugging

answered Mar 17 '18 at 22:36

Naveed Ahmad

6,627
2
58
83

1

I faced with this issue in android studio 4.1 and your solution helped me. Thanks – Buckstabue Oct 19 '20 at 14:44

score 1 · Answer 29 · answered Sep 17 '18 at 15:33

<application android:debuggable="true">
</application>

That above code is not longer a solution. You need to enable debugging inside your build.gradle file. If you have different buildTypes make sure you set "debuggable true" in one of the build types. Here is a sample code from one of my projects.

buildTypes {
    debug {
        debuggable true
    }

    release {
        debuggable false
    }
}

**I have deleted other lines inside the buildTypes which are not relevant to this question from my gradle file here.

Also Make sure you select the correct build variant in your android studio while doing the debugging.

score 1 · Answer 30 · answered May 19 '19 at 16:23

Over the years I have visited this thread many times and there was always a different response that helped me. This time I figure out that it's my USB hub that was preventing debugger to work properly. As strange as it sounds, instead of having a phone connected to my computer via a USB hub, I had to connect it directly to my mac and debugging started to work.

score 0 · Answer 31 · answered Nov 11 '16 at 06:10

Here's a little oops that may catch some: It's pretty easy to accidentally have a filter typed in for the logcat output window (the text box with the magnifying glass) and forget about it. That which will potentially filter out all output and make it look like nothing is there.

score 0 · Answer 32 · answered Mar 21 '17 at 11:19

0

In my case I had the same problem because I try to debug signed apk. In my gradle config I made differents build variants, and try to debug release build with production keystore.jks

answered Mar 21 '17 at 11:19

WorieN

1,276
1
11
30

score 0 · Answer 33 · answered Nov 28 '18 at 12:15

0

What worked for me in Android Studio 3.2.1

Was:

RUN -> Attach debugger to Android Process --> com.my app

answered Nov 28 '18 at 12:15

Kevin Amiranoff

13,440
11
59
90

score 0 · Answer 34 · answered Apr 27 '21 at 13:35

My problem was:

i was using other debug app apart from my current project in AS.
when i click on 'attach to debugger' it was saying "there is no process with com.xyz.abc.appname"

This helped me: just after 'make project/build' button, there is 'select run/debug configuration' > go to 'Edit configuration' The configuration is shown in the image. then my debugger started working.

score 0 · Answer 35 · answered Sep 24 '22 at 07:52

I'll add this not because it's the solution to the question, but I've not seen it anywhere else. If you're running a custom OS and the only debuggable apps listed in Android Studio are the low level ones (probably Qualcomm stuff), you may be debugging as root. If whoami within adb shell shows your name as root, try running adb unroot. Your name should now be shell. Then try debugging again.

score 0 · Answer 36 · answered Nov 04 '22 at 10:49

0

A simple cold boot from device manager menu solved this for my emulator.

answered Nov 04 '22 at 10:49

Dean Delicata

31
3

score -2 · Answer 37 · answered Jun 29 '20 at 10:22

-2

Sync your project with Gradle files and that shall help.

answered Jun 29 '20 at 10:22

Rahee

195
1
5

don't work. what works was restart adb server: https://stackoverflow.com/a/60805797/4628993 – Acauã Pitta Mar 17 '22 at 19:56

score -3 · Answer 38 · edited Nov 26 '14 at 06:54

-3

I had same problem and I tried almost all kinds of solutions via Google. But I couldn't solve it. Finally, I found the solution. This is Android Studio Bug.

Do not click Run (Alt + F10) — just click Debug (Shift + F9).

Then Android Studio will show you the Warnning Message with ADB, Then Just click "OK".

You can see log in logcat console. And Packages will be shown on DDMS(Devices).

edited Nov 26 '14 at 06:54

Ajith Renjala

4,934
5
34
42

answered Nov 26 '14 at 06:16

Guest

11

Not Able To Debug App In Android Studio

38 Answers38

Linked