IssueTracker

can you share your android studio version

Is this happening with Studio 3.0?

Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).

Hi, also happened on Mac Book Pro 15 retina mi-2015
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.

The issue is still there in Android Studio 1.1.0 and the Gradle plugin 1.2.0-beta1.

I'm seeing the same thing using Android studio 1.1.0 and Gradle 1.1.0

The same for Android Studio 1.2 Beta and Gradle plugin 1.2.0-beta1

Removing "useJack = true" from gradle script helped me to solve this issue.

I have the problem only my windows 8.1 machine, not on my mac.

Same here.

Debugger doesn't see variable passed in to method, regardless of where in the method the execution point is.

Not using 'useJack' command,
Android Studio 1.2 beta 2
Gradle plugin 1.10

Same issue.

Lastest Android Studio (1.2 - Canary channel)
Android Gradle 1.2.2

Gradlew clean, followed by a invalidate caches / restar helps, but it is so slow...

Similar issue here...  However, it happens when debugging test builds.  I am not able to evaluate local variables in the target code, but I _am_ able to evaluate local variables in the test code.

Multidex enabled.
Gradle 1.1.3
Android Studio AI-141.2024585 (June 18th, 2015)
Using an emulator with Android 5.0

For those who are still seeing this, check if your problem is the one described in Issue 36949180.

Same bug for Android Studio 2.0 PREVIEW 4.

This problem intermittently shows up for me.  I'm running Android Studio 1.5.1.  This is a pretty basic and commonly used feature--I'm quite surprised to see it still hounding Android Studio.

THe bug is still there (AS 2.0 Beta 5).

Why is this still not fixed?

AS 2.1 looks working (for now)

I had this issue in both AS 1.5.1 and AS 2.0 preview (using plugin 2.0.0-beta6) until I removed "testCoverageEnabled true" from my debug buildType. I suspect JaCoCo's bytecode manipulation interferes with the debugger.

Android Studio 2.0, JRE 1.8. Problem appeared in one place (final array local variable). Adding testCoverateEnabled true helped to see those variables. I can't see arguments sent to methods though.

[Comment deleted]

Android Studio 2.1, gradle 2.1.0 Java 1.8. Not able to see any local variables

I resolved problem with gradle 1.3.0 using. Gradle 2.1.0 do something wrong and local variables are not founded.

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!

Is there a new ticket for the jack related problem?

Would be nice to be able to see local variables during debug when Jack toolchain is enabled...

Any update on this?

Removing "testCoverageEnabled true" fixed the issue for me.

Reopening as an issue specific to the situation when Jack is enabled.

Same issue is with me. i am using android 2.1.3 and gradle version 2.14.1 and java version is 1.8  any idea how can i fix it

When generating dex that is not optimized, debugging info can be wrong.

1. Have you specified to not optimize dex in android.dexOptions.optimize?
2. Can you provide repro project or steps?
3. Can you upload your build.gradle?

Thanks

apply plugin: 'com.android.application'

android {
    compileSdkVersion 24
    buildToolsVersion "24.0.2"

    defaultConfig {
        jackOptions {
            enabled true
        }
        applicationId "com.example.sundeep"
        minSdkVersion 16
        targetSdkVersion 24
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
        debug {
            testCoverageEnabled  false
        }
        debuggable.initWith(buildTypes.debug)
        debuggable {
            testCoverageEnabled = false
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
}



dependencies {
    compile fileTree(include: ['*.jar'], dir: 'libs')
    compile 'com.android.support:appcompat-v7:24.2.0'
    compile 'com.android.support:design:24.2.0'
}

Which device are you using for debugging?

Samsung Note 3

It really frustrating for me. If you have any info then please provide me

Any body able to find out solution or its a bug. Please let me know

I have the same problem while using Java 8 and Jack Toolchain.

Using
Android Studio 2.1.3
gradle:2.1.3
compileSdkVersion 24
buildToolsVersion "24.0.2"

I had to temporarily disable Jack and use Gradle Retrolambda Plugin instead.

The issue should be fixed in the newest Android Studio, 2.2-beta3 (http://tools.android.com/download/studio/canary). Please try with that version and open a new issue if the issue still happens.

Yes this issue is fixed in Android Studio v2.2 beta3 but you have to use Gradle-2.2.0-beta3 for the debugger to show variables value. So the problem was with gradle not android studio. Anyway thanks to everybody

Just Now I have tested debugger is showing variables values with Android v2.1.3 after using Gradle v2.2.0Beta3. So basically we have to use Gradle v2.2.0Beta3

@#39 AndreiNi...@gmail.com thanks. Your solution worked for me !!

#41 I'm using AS 2.2 final and gradle 2.2.0 final and still see this problem so no, that's not the problem

still have this question AS  2.2 release version

If any of you continue to see problems, please file a new bug referencing this one, and include a test case that demonstrates the problem. Thanks!

AS 3.1 and this is still happening...

encountered this bug when I am debugging signal android https://github.com/signalapp/Signal-Android
AS 3.2.1

Still having this bug on Android Studio 3.2.1 for release version with `android:debuggable="true"` set.

4/21/2020 I am still having this bloody error and it's driving me crazy and I have the latest android studio version.