Android Studio - Coverage instrumentation results in dx dropping LVT entries for method parameters [37019591]

Fixed

Bug

Migrated-Tools-debugger

[AOSP] duplicate

[AOSP] NotEnoughInformation

NeedsInfo

Migrated-Tools-Gradle

Migrated-Tools-Studio

Status Update

No update yet.

Description

la...@gmail.com

created issue #1

Jan 30, 2015 09:15PM

Since I moved my project from ANT to gradle, I have had problems with debugging in Android Studio. The problem I am having is that when I try to debug my code, I can see variables that are created in the method and also any instance variables, however, any variables defined as method parameters are not visible. Android studio say the could not be found.

What I found was that in my build.gradle file, the buildTypes.debug caused the problem when
"testCoverageEnabled true" was present. If it wasn't present, then I could see the parameters when debugging. I believe the original reason I had this field there was because I was trying to get code coverage results from Jacoco.

buildTypes {
debug {
versionNameSuffix '-DEBUG'
testCoverageEnabled true // This line when included causes problem
debuggable true
}
release {
minifyEnabled false
debuggable false
}
}

Comments

vs...@google.com <vs...@google.com> #2Jan 30, 2015 10:09PM

Assigned to ra...@google.com.

can you share your android studio version

la...@gmail.com <la...@gmail.com> #3Jan 30, 2015 11:14PM

Is this happening with Studio 3.0?

ra...@google.com <ra...@google.com> #4Feb 2, 2015 06:15PM

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).

ra...@google.com <ra...@google.com> #6Feb 3, 2015 11:52PM

Reassigned to be...@google.com.

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.

st...@gmail.com <st...@gmail.com> #7Feb 12, 2015 12:44PM

People looking for a quick workaround can add a new buildType based on debug, but with the property changed.

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

Just use that buildType when you're going to be debugging without needing to flip a value back and forth if you actually need the coverage for another process.

ap...@gmail.com <ap...@gmail.com> #8Mar 25, 2015 05:04PM

I'm also having this issue. Gradle plugin v1.1.1, Intellij 14.1.

ap...@gmail.com <ap...@gmail.com> #9Mar 25, 2015 05:04PM

I'm also having this issue. Gradle plugin v1.1.1, Intellij 14.1.

ba...@gmail.com <ba...@gmail.com> #11Jun 10, 2015 06:36PM

same issue here: Gradle 2.4, Studio 1.2.1.1, Mac OS

ni...@luxe.com <ni...@luxe.com> #12Jun 22, 2015 09:00PM

[Comment deleted]

ni...@gmail.com <ni...@gmail.com> #13Jun 22, 2015 09:01PM

Same here, Android Studio 1.3 (AI-141.2017176), SDK Tools: 24.3.1

ko...@gmail.com <ko...@gmail.com> #14Aug 26, 2015 04:27PM

Any chances this bug will be fixed in a visible future?

vs...@google.com <vs...@google.com> #17Dec 3, 2015 07:54PM

Ref internal bug:

b/25998400

[Deleted User] <[Deleted User]> #18Dec 8, 2015 12:13PM

its coming for me android studio v2.

pa...@gmail.com <pa...@gmail.com> #19Jan 2, 2016 02:12PM

Cannot find local variable in debug mode for Android Studio 2.0 PREVIEW 4.

da...@gmail.com <da...@gmail.com> #21Feb 29, 2016 05:15AM

I suggest you rebuild Android Studio starting from scratch

a....@gmail.com <a....@gmail.com> #22Feb 29, 2016 07:04AM

Issue seems to be still present in AndrodiStudio 2.0 beta6.
This is nonsense - not letting people to debug on Android for more then a year already!

ty...@gmail.com <ty...@gmail.com> #23Mar 21, 2016 10:55PM

Also seeing this issue on 2.0 beta 6.

d....@googlemail.com <d....@googlemail.com> #24Apr 12, 2016 10:03AM

Problem exists in AS 2.1 preview 4

lu...@gmail.com <lu...@gmail.com> #25Apr 21, 2016 11:21PM

What is the solution for this ?
Please fix this !

ty...@gmail.com <ty...@gmail.com> #26Apr 27, 2016 08:16PM

Just updated to the Stable Release of 2.1 and I just started having this problem

da...@gmail.com <da...@gmail.com> #27Apr 28, 2016 11:06AM

Having this issue with gradle 2.0.0, 2.1.0, Android Studio 1.5.1, 2.0.0, 2.1.1. The issue appeared like a week ago, thought it's the 2.0.0 version I installed but apparently it's something else. Really annoying, can't code basically.

ar...@gmail.com <ar...@gmail.com> #28May 10, 2016 06:55AM

I am facing this issue since I updated to 2.1 stable version, its really frustrating that I cannot debug my application, will this be fixed soon?

ba...@gmail.com <ba...@gmail.com> #29May 23, 2016 07:02PM

Android Studio 2.1.1, same problems.
buildToolsVersion '24.0.0 rc1'
gradle:2.1.0'

debug {
versionNameSuffix '-DEBUG'
testCoverageEnabled = true
debuggable true
jniDebuggable true
renderscriptDebuggable true
minifyEnabled false
zipAlignEnabled false
}

[Deleted User] <[Deleted User]> #31Dec 22, 2016 12:28AM

I saw this bug in Android Studio version 2.2.3 with Build-tools version 25.0.2. The 'quick workaround' worked.

iv...@justeattakeaway.com <iv...@justeattakeaway.com> #32Jan 9, 2017 03:28PM

Appeared for me on gradle 2.2.3 build tools 24.0.3

mi...@gunt.li <mi...@gunt.li> #33Feb 6, 2017 04:00PM

Seeing the same issue.

Versions:
Android Studio: 2.2.3
Gradle: 2.14.1
SDK Build Tools: 25.0.2

[Deleted User] <[Deleted User]> #34Apr 6, 2017 03:51PM

I have the same problem, Android Studio: 2.3, Gradle: 2.3.0

di...@gmail.com <di...@gmail.com> #35Apr 20, 2017 08:07AM

Similar issue that others reported here -- It's painful to have the work around be a separate buildType for this especially for multiple modules that don't actually need this. Almost two years with this bug I think it's high time you do something about it.

gu...@gmail.com <gu...@gmail.com> #36May 2, 2017 02:41PM

I have to agree, if there is no one working on this issue, At least removed the assignee label.

pa...@wisner.org <pa...@wisner.org> #37Jun 13, 2017 07:29PM

Seeing this issue in Android Studio 2.3.1, gradle 2.3.1
The issue goes away when I change "debug { testCoverageEnabled = false; }" instead of true.

ma...@appsflyer.com <ma...@appsflyer.com> #38Aug 6, 2017 01:08PM

Same here:
Android Studio: 2.2.3
Gradle: 3.3

zu...@gmail.com <zu...@gmail.com> #39Sep 7, 2017 08:35AM

What's the status of this issue as of Sep 7, 2017?

ja...@gmail.com <ja...@gmail.com> #40Oct 2, 2017 07:49PM

What about as of Oct. 2, 2017?

[Deleted User] <[Deleted User]> #41Oct 19, 2017 10:34AM

Still reproducible in Android Studio 3.0 RC1, Gradle Plugin: 3.0.0-rc1
I am using Kotlin if it makes a difference

sz...@gmail.com <sz...@gmail.com> #42Nov 8, 2017 02:00PM

Issue still reproducible with:
Android Studio 3.1 Canary 2
Android Gradle Plugin: 3.0.0
Build Tools: 26.0.2
Gradle: 4.2.1

mi...@gmail.com <mi...@gmail.com> #43Nov 9, 2017 04:30PM

Issue still reproducible with

Android Studio 3.0
Android Gradle Plugin: 2.3.3
Build Tools: 26.0.02
Gradle: 4.3.1

cm...@trulia.com <cm...@trulia.com> #44Mar 7, 2018 12:36AM

Still an issue with 3.1.

:(

ja...@gmail.com <ja...@gmail.com> #45Mar 23, 2018 07:31AM

I am using proguard in release build mode but I have several other lib projects as dependency. When I try to build project in debug mode proguard still runs. After adding -dontobfuscate in progaurd rule I am not able to see the debug information.

[Deleted User] <[Deleted User]> #46Sep 24, 2018 07:58PM

Hey Google, are you serious about testing? This issue is listed since Jan 30 2015. When can we expect a fix?

bd...@google.com <bd...@google.com> Sep 24, 2018 11:42PM

Reassigned to ag...@google.com.

ag...@google.com <ag...@google.com> Sep 25, 2018 07:47AM

Reassigned to ze...@google.com.

ze...@google.com <ze...@google.com> #47Sep 25, 2018 12:36PM

Marked as fixed.

This issue reproduces in Studio 3.2 with android.enableD8=false to force using the DX compiler. (A new empty app with debug and test coverage will not display the savedInstanceState formal parameter of MainActivity::onCreate)

When setting android.enableD8=true (the default value for studio 3.2) the locals information is preserved and is visible in the debugger.

The locals are not visible before PC 0x4 since Jacoco inserts code without regard for the local variable table, but the locals do become visible as soon as the debugger has advanced past the inserted instructions.