Cannot see parameter value in Android Studio when breakpoint is in first line of a method

Question

I am just switching from Eclipse to Android Studio and found this weird behavior. When I add a breakpoint in the first line of a method, I cannot see the parameter values. The only thing I can see then is the this reference. I either have to make one debug step or set the breakpoint to a line after the first one to see the parameter values.

Anyone else has this problem or knows what's going wrong here?

possibly your code and what is running are not in sync, and there is an extra line somewhere. Try to clean, install and run again. — njzk2, Jan 12 '15 at 19:51
Yea, i did that multiple times. I cleaned the project and restarted the IDE. Still the same... — SimonSays, Jan 12 '15 at 19:58
I have the same problem. It has nothing to do with synchronization. — Hazen Hills Software, Jan 29 '15 at 00:32
How do we report it? I couldn't find an obvious link on Android Tools projects site. — lazypig, Jan 29 '15 at 01:10
Bug reported here https://code.google.com/p/android/issues/detail?id=119564&thanks=119564&ts=1422496187 — SimonSays, Jan 29 '15 at 01:50

score 39 · Answer 1 · answered Aug 13 '15 at 07:04

39

Try turning off your jacoco test coverage off for the debug build in your build.gradle file:

debug {
    ...
    testCoverageEnabled false
}

This completely fixed the issue for me where upgrading the gradle plugin did not.

answered Aug 13 '15 at 07:04

Rhys Davis

996
7
16

This worked for me. BTW, this snippet should be in the app build script, mine is in the "android" section of that script. The android issue tracker includes issue [177480](https://code.google.com/p/android/issues/detail?id=177480&q=debug%20arguments&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars) which includes this answer, as well as some other recommendations on the topic. – OYRM Jan 09 '16 at 22:09
Don't know why, but this seems to have worked for me too. So the problem is jacoco? – SMBiggs Feb 10 '16 at 17:42
this should be the accepted answer, am using gradle plugin 2.0.0 and still had this issue. This one fixed it for me. – kev Jun 28 '16 at 07:35
2

Worked for me. Why is this happening though... I shouldn't have to turn off jacoco to debug -.- – Ryan Newsom Sep 09 '16 at 16:49

Guillermo Orellana Ruiz · Answer 2 · 2016-09-25T21:59:04.243

7

A good solution until AOSP Issue #123771 is solved, is to use the snippet provided by Stuart in the comments section:

buildTypes {
    debug {
        [...]
        testCoverageEnabled true
    }
    release {
        [...]
    }
    debuggable.initWith(buildTypes.debug)
    debuggable {
        testCoverageEnabled false
    }
}

This way you can both keep your test coverage reports in your debug build and have a way of stepping through code seeing your local variables.

edited Sep 25 '16 at 21:59

answered Dec 16 '15 at 12:13

Guillermo Orellana Ruiz

734
8
19

This didn't work for me (at least not in espresso tests) – loeschg Jun 15 '17 at 16:21

IgorOK · Answer 3 · 2016-09-29T23:07:30.607

2

I don't have in my gradle file:

debug {
    ...
    testCoverageEnabled true
}

but had the same issue on Android Studio 2.2. Solution that helped me to resolve issue:

Disable Instant Run in IDEA Settings.
Re-build project.
Enable Instant Run.

edited Sep 29 '16 at 23:07

answered Sep 29 '16 at 23:02

IgorOK

1,652
4
18
36

1

I had Instant Run disabled because of this https://stackoverflow.com/questions/40618803/android-app-crashes-when-launched-in-debug-mode and then breakpoints worked again after reenabling. – rob5408 Oct 17 '17 at 19:25

score 1 · Accepted Answer · answered Jan 29 '15 at 18:31

1

The solution provided by Google here is to upgrade the Android Studio Gradle plugin to v1.0.1

answered Jan 29 '15 at 18:31

SimonSays

10,867
7
44
59

Miklós Keresztes · Answer 5 · 2016-06-16T20:10:30.547

1

If your build uses the jack toolchain this can be the source of the problem. In my case, disabling jack solves the problem:

buildTypes {
...
    debug {
        jackOptions {
            enabled false
        }
    }
}

Note: 1.8 source compatibility requires jack!

edited Jun 16 '16 at 20:10

answered Jun 16 '16 at 19:19

Miklós Keresztes

180
2
5

score 1 · Answer 6 · answered Nov 08 '16 at 04:29

I got sick of toggling testCoverageEnabled when I wanted to debug so set up a project property to disable it when run from Android Studio, but default to enabled when run from command line with no options such as on a build box.

// Default to true, set -PtestCoverageEnabled=false in IDE compiler command-line options
def isTestCoverageEnabled = { ->
    def enabled = project.hasProperty('testCoverageEnabled') ? testCoverageEnabled.toBoolean() : true
    println "testCoverageEnabled = " + (enabled ? "true" : "false")
    return enabled
}

android {
    buildTypes {
        debug {
            testCoverageEnabled isTestCoverageEnabled()
        }
    }
}

To set the property in the IDE add the command-line option -PtestCoverageEnabled=false

Android Studio -> Preferences -> Build, Execution, Deployment -> Compiler -> Command-line Options

score 0 · Answer 7 · answered Jul 15 '18 at 03:32

0

I ran into this issue when trying to debug an app that was previously installed using an APK and not from Android Studio itself. Fixed it by uninstalling the app and re-run the debug.

answered Jul 15 '18 at 03:32

Chin

19,717
37
107
164

score 0 · Answer 8 · answered Feb 20 '19 at 12:09

0

Following configuration worked for me for buildType release.

buildTypes {

release{

testCoverageEnabled = false

debuggable true

minifyEnabled false

shrinkResources false

}

answered Feb 20 '19 at 12:09

DkPathak

452
1
4
16

Cannot see parameter value in Android Studio when breakpoint is in first line of a method

8 Answers8