android debugger does not stop at breakpoints

Question

I am seeing debug statements in the console but the debugger does not stop on any breakpoints. I tried clearing all breakpoints and adding them back in. Not sure how this can happen but it is.

Hardee

My solution was reinstalling Eclipse. Possible weaker solutions are: workspace cleaning (remove all eclipse file and import from the resulting project; Clean Project, Restart Eclipse. – Monochromatism

Answer 1

Have you set the debuggable flag in the AndroidManifest? If you miss that, do so by adding android:debuggable="true" in the application tag. It should look like that in the end:

<application android:icon="@drawable/icon" android:label="@string/app_name" android:debuggable="true">

Pentaprism

And in the my case it won't help :-( – Monochromatism

@Wooff you should post that as a separate answer. :) – Doan

@Wooff as if I don't have enough files littering my dev folder. Are you saying I need another "debug" folder. I think Linux would be a more maintainable solution. – Yate

Android Studio does not support this flag anymore. – Hangdog

@ZdravkoDonev debuggable flag is now defined in build.gradle (see developer.android.com/studio/build/build-variants#build-types) – Cassaba

@Monochromatism have you founded any solution? – Threeply

@BhunnuBaba Yes, reinstalling Eclipse. Weaker solutions are: workspace cleaning (remove all eclipse file and import from the resulting project; Clean Project, Restart Eclipse. – Monochromatism

I tried the solution but the android studio won't let me and shows me the message Avoid hardcoding the debug mode – Lafountain

Answer 2

Solution that worked for me:

• Simply uninstall the app from the device (manually on the device) and try debugging again(!)

Capillarity

You can't do easier than that =) – Yashmak

Thanks! Worked fine! – Hypnogenesis

That's rigth! On new phone I've tried Run and then Debug. After that breakpoints stopped work. After uninstall app from phone and rerun Debug mode, breakpoints started work again – Christinachristine

I finally found the ultimate solution for my worst nightmare using Android Studio! – Gamogenesis

I've been using Android Studio for years and have never had to do this. No idea what changed, but I just tried uninstalling it and it worked! Thanks! – Bifocals

Try the solution from @Tibbetts - "Attach debugger to Android process", it may save you this trouble. – Panteutonism

This works for me even for flutter as well – Maeda

Answer 3

If you use Android studio, click debug app instead of run app:

Cynthea

Silly me! +1. This should be the accepted answer. Android studio warns you against putting android:debuggable="true" in the application manifest which is suggested in the accepted answer. – Hadik

Answer 4

According to this answer, Inside build.gradle for your app module, disable minifyEnable for your build variant and change it to false. Then, it should be:

minifyEnabled false

othewise you will see Line number not available in class xxxx when you hover over breakpoint markers and they will be looked with a cross on them

Tiger

I will add that I did not see the mentioned message when hovering the breakpoint. Non-working breakpoint were missing a little checkmark on it essentially leaving them as a plain red circle whereas the working breakpoints had this checkmark. – Waterlog

Answer 5

In my case, click the "Attach debugger to Android process"

And it will shows a window said "Choose Process" Select the device you are using, and select the project that you want to debug. And it works.

Sometimes the debugger need to re-attach to the devices when you open the debugger at the first time.

Tibbetts

Answer 6

For Android Studio:

• Check if the option Mute Breakpoints is enabled by mistake. The icon looks like this:

For Eclipse:

• Check if the option "Skip All Breakpoints" is enabled by mistake. It is the last icon on the following toolbar

Daryl

Where can I find this option in android studio? – Anklet

In Android Studio, "Mute Breakpoints" option is present inside Debug view. Check my edited answer. – Daryl

Answer 7

Did you do "Debug As --> Android Application" instead of "Run As"?

Only if you do "Debug As", eclipse will stop at breakpoints.

Aestival

Answer 8

I had the same problem. Go to build.gradle. You must change this code if you have one.

buildTypes {
    release {
        minifyEnabled true
        shrinkResources true
        proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
    }
    debug {
        debuggable true
        minifyEnabled true
        shrinkResources true
        proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
    }
}

The debug section should look like this:

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

I hope your problem is solved

Crimpy

Answer 9

In my case, the app created a service with a different process with android:process=":service" in the AndroidManifest. So I was setting breakpoints in the service process code while the debugger is automatically attached to the main app process. Pretty stupid of me but it might help someone else.

You attach to the service process with Run > Attach Debugger To Android Process and choose the service process. You might need to add android.os.Debug.waitForDebugger(); to your service process code if you can't attach in time manually.

As far as I know, there's no way to automatically tell Android Studio or IntelliJ to attach to a different process before running.

Crenel

Answer 10

if you have added some build type in build.gradle check to have debuggable true

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

    release {
        minifyEnabled true
        proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
    }
}

Imagine

I had no debug config but adding one like the above solved my problem. – Percaline

Answer 11

i had this problem i clean buildTypes part of build.gradle and try age so it work me.

Edelstein

Answer 12

If you are finding this issue while using the Flutter plugin, you can try updating the plugin to version >65.1.3 as specified in this article

Cummine

Answer 13

None of the valid answers above worked for me. In my case there was another app still in the background that I had launched some time earlier via Android Studio. So not the same App/PackageId, but another. After closing that app I got hits on breakpoints via wifi debugging.

Epicenter

Answer 14

I had the same issue and resolved it by increasing the debugger timeout values. The emulator is slow as a dog on my Dev box and that is what prevented the debugger to catch and stop on breakpoints. I changed the timeout values respectively from 3000 to 10000 and 20000 to 60000 and all is fine now.

V.

Ilailaire

Where do you set the debugger timeout values? I think I have the same problem as you, because the debugger catches on every breakpoint when I debug on a physical device, but most often fails to catch on the first breakpoint I set when I debug on the emulator. -Sarah – Implicatory