Android studio gradle breakpoint No executable code found at line

Question

I am developing an android application using Android Studio 2.1.3 and gradle.

The problem is that the breakpoint in a simple method is never hit, although it must be hit because the condition is met during application debugging.
First, I thought that the problem is related to the issue described in the answer for this question: BuildConfig.DEBUG always false when building library projects with gradle

To test this, I removed library project and integrated all my source code into the main app module. It solved nothing. To be noted that the following is the build.gradle, where minify is set to false for both debug/release:

apply plugin: 'com.android.application'  

android {  
    compileSdkVersion 23  
    buildToolsVersion "23.0.2"  
    defaultConfig {  
        applicationId "com.mycompany.mymobileapp"  
        minSdkVersion 21  
        targetSdkVersion 21  
        versionCode 1  
        versionName "1.0"  
    }  
    buildTypes {  
        release {  
            minifyEnabled false  
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'  
            debuggable true  
            jniDebuggable true  
            renderscriptDebuggable true  
            zipAlignEnabled false  
        }  
        debug {  
            debuggable true  
            minifyEnabled false  
            zipAlignEnabled false  
            jniDebuggable true  
            renderscriptDebuggable true  
        }  
    }  
    productFlavors {  
    }  
}  
  
dependencies {  
    compile fileTree(include: ['*.jar'], dir: 'libs')  
    testCompile 'junit:junit:4.12'  
    testCompile 'org.mockito:mockito-core:2.0.5-beta'  
    testCompile 'com.android.support:support-v4:23.1.1'  
    testCompile 'org.powermock:powermock-api-mockito:1.6.2'  
    testCompile 'org.powermock:powermock-module-junit4-rule-agent:1.6.2'  
    testCompile 'org.powermock:powermock-module-junit4-rule:1.6.2'  
    testCompile 'org.powermock:powermock-module-junit4:1.6.2'  
    compile 'com.android.support:appcompat-v7:23.1.1'  
}

Here is the screenshot with what Android Studio shows to me:

This is also not the only case. It happens that the compiler, while Stepping over, jumps to completely another part of the code than the one being debugged.

Is there any reasonable explanation here? Suspend: "thread" and "all" tried, same result.

UPDATE 1: Re-created the project using Eclipse, and everything works fine. It is still amazing why using Android studio this does not work!

I've tried everything and didn't work. Gotta love being an Android Developer it's the worst — DennisVA, Oct 19 '21 at 20:27

score 60 · Answer 1 · edited Oct 12 '19 at 10:37

60

buildTypes {

release {
    minifyEnabled true
    shrinkResources true
    proguardFiles getDefaultProguardFile('proguard-android.txt')

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

    }
}

Set minifyEnabled false in debug block in build.gradle file.

edited Oct 12 '19 at 10:37

Tamir Abutbul

7,301
7
25
53

answered Dec 29 '16 at 06:13

vinod

1,126
13
18

3

I have this line in my gradle and still have the issue – Quinn Jan 23 '20 at 19:43
1

And what if we want to use minify? – Matt Apr 17 '20 at 06:58

score 8 · Accepted Answer · answered Oct 05 '16 at 14:40

8

After re-creating the application using Eclipse and observing the correct behavior, I returned to Android Studio in order to check if there is any option that I missed.

After trying all the options from File -> Settings that I could, I made the conclusion that Instant Run is the evil that caused me to waste so much precious time.

I don't understand how it is related with my problem, but after clearing all check-boxes:

I ended up with a code that executes the way I as a developer expect:

answered Oct 05 '16 at 14:40

XMight

1,991
2
20
36

1

In my case it was happening all the time. You want to argue with C, C++, C# and Java many editors and 6 years experience and tell me that I don't know how to clean a project? Please don't write such useless comments anymore. Sadly I can't down-vote your comment. Also, this is not happening to me alone. Discussed with many other full-time Android developers after this and they have the instant instant run turned off by default because of bugs like this. – XMight Oct 30 '16 at 14:54
2

Enable Instant Run, clean project -> Result: breakpoint not hit. Disable Instant Run, clean project -> Result: breakpoint hit. Happens right now. I'm on a Windows 8.1 Pro Machine, maybe this is the problem. – XMight Oct 31 '16 at 16:01
Yes maybe platform related or version related I am on 2.2.2 and osx. I suggest you upgrade to 2.2.2. Here clean works always, but my build times with clean are terible on this computer. – Renetik Oct 31 '16 at 18:13
It did solve my problem. thank you for saving carbon foot prints :)) – Waterfr Villa Oct 20 '17 at 17:28
1

Cut(ctrl+X) the method and pasting somewhere else in the class worked for me.. Crazy:) – Akshatha S R Dec 08 '17 at 11:37
The `Instant run` option no longer exists in the latest Android Studio unfortunately. – andras Jan 19 '22 at 17:30

Raza · Answer 3 · 2018-01-10T22:58:16.497

6

I was facing a similar issue.

I've tried:

Cleaning the Project
Resetting Android Studio
Rebuilding the project
Disabling the Instant Run

and it didn't work.

All I did in the end to make it work was Ctrl+Shift++. That is the shortcut for expanding all code blocks. I just ran the project after that and it worked.

edited Jan 10 '18 at 22:58

answered Jul 12 '17 at 08:59

Raza

831
9
10

3

Did the same, and nothing helped. -_- Crazy. – garbus Jan 08 '18 at 22:23
1

Expanding all code blocks worked for me. Seems like a bug from Android Studio Arctic Fox. – ThiagoYou Aug 19 '21 at 18:48

score 6 · Answer 4 · answered Mar 31 '20 at 14:42

6

It`s problem with studio cache.
File -> Invalidate Caches / Restatrt... May help you.

answered Mar 31 '20 at 14:42

user2183539

246
4
5

When in doubt, Invalidate and Restart! (It's your daily exercise regimen.) – SMBiggs Aug 30 '21 at 19:20

score 2 · Answer 5 · answered Oct 04 '16 at 15:05

2

try to clean and rebuild the project. try to make some log in this method to check if the it being executed.

LOG.(TAG,"method being executed")

answered Oct 04 '16 at 15:05

Chenmin

121
7

Clean is good workaround but where is the bug report for this isssue, I should vote for fix ? I have to wait 4 mins after I hit clean thats not too much Instant Run. – Renetik Oct 28 '16 at 18:24
You may have inadvertently added code in that file since deploying it in the debugger, throwing off the line correlation. Clean and redeploy. – Lucy Apr 30 '21 at 09:14

score 2 · Answer 6 · answered Aug 18 '21 at 10:12

I had the same problem as you did. I think that happened for some reason while I was cleaning up my code and I was collapsing some of my code blocks.

The solution was to use the shortcut CTRL + SHIFT + + to expand all of my code blocks and then to click File>Inavlidate Caches/Restart...

I am using Android Studio Arctic Fox | 2020.3.1 and build:gradle:4.1.3

score 1 · Answer 7 · answered Mar 23 '20 at 10:26

Uninstalling and installing the App on the test device solved my issue.

I tried:

Cleaning/rebuilding the Project
Resetting Android Studio, Clean Cache
Setting the debugger to stop on all threads
There is no minifyEnabled in my debug variant.

Disabling the Instant Run wasn't an option as of Android Studio 3.6 so I didn't try it. see this StackOverflow question

score 1 · Answer 8 · answered Aug 10 '22 at 05:49

1

In my case, the problem was Build Variants was set to release, which of course is not a debuggable build.

(I forgot about setting that previously to try profiling.)

answered Aug 10 '22 at 05:49

Jerry101

12,157
5
44
63

score 1 · Answer 9 · answered May 09 '23 at 10:36

Another reason why the breakpoint doesn't work might be, that you've placed it in a source code which is not used in runtime.

In my case, I work with multiple modules/dependencies. Therefore, if I want to place a breakpoint e.g. in RecyclerView, I have to take care which version will be used in runtime since Android Studio suggests all the available sources (press Ctrl+N two time).

score 0 · Answer 10 · answered Sep 16 '19 at 17:00

0

Restart Android Studio

If you know that nothing was changed that can cause this since it was working before. Then try by closing and restarting Android Studio. That worked for me on Android Studio 3.5.

Clean build did not work for me

answered Sep 16 '19 at 17:00

HBB20

2,743
1
24
35

score 0 · Answer 11 · answered Mar 10 '22 at 21:44

0

I was facing a similar issue.

add in your file build.gradle

DEV {
      initWith debug
    }

answered Mar 10 '22 at 21:44

Devix

432
5
16

score -3 · Answer 12 · answered Jun 06 '21 at 13:15

-3

Make sure you don't misspell the file name and the class name.

answered Jun 06 '21 at 13:15

neevek

11,760
8
55
73

Android studio gradle breakpoint No executable code found at line

12 Answers12

Linked