AGP 8.0.1 release package jacoco instrument does not take effect [283015405]

Fixed

Bug

NeedsInfo

Status Update

No update yet.

Description

co...@gmail.com

created issue #1

May 17, 2023 02:17AM

AGP version: 8.0.1
buildTypes {
release {
minifyEnabled true
testCoverageEnabled true
....
}
}
I set minifyEnabled & testCoverageEnabled as true, but jacoco instrument does not take effect, and obfuscation also did not work.

buildTypes {
release {
minifyEnabled true
enableAndroidTestCoverage true
....
}
}
I set minifyEnabled & enableAndroidTestCoverage as true, obfuscation does work, but jacoco instrument does not take effect.

Comments

mk...@google.com <mk...@google.com> #2May 17, 2023 06:55AM

for example, many different devices return the same longitude and latitude.such as : longitude is 121.474000 and latitude is 31.230001.
i donnot understand why is the data the same?

co...@ringcentral.com <co...@ringcentral.com> #3May 18, 2023 02:26AM

Comment has been deleted.

Message last modified on May 18, 2023 02:27AM

co...@gmail.com <co...@gmail.com> #4May 18, 2023 02:29AM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

What steps are needed to reproduce this issue? Frequency of occurrence?

Which Android build are you using? (e.g. AP4A.241205.013.A1)

Which device did you use to reproduce this issue?

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

ha...@google.com <ha...@google.com> May 18, 2023 06:12PM

Assigned to an...@google.com.

an...@immobiliare.it <an...@immobiliare.it> #5May 21, 2023 01:18PM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

Message last modified on May 21, 2023 01:18PM

je...@google.com <je...@google.com> May 24, 2023 05:59PM

Reassigned to ga...@google.com.

ga...@google.com <ga...@google.com> #6May 25, 2023 03:00PM

Reassigned to lu...@google.com.

I only aply permission android.permission.ACCESS_COARSE_LOCATION.I use android.location.Location in the program.
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。

as for Android build,all versions have it.
I dont reprodouce this issue.

what may be the cause of this issue?please

lu...@google.com <lu...@google.com> #7May 25, 2023 03:51PM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

co...@ringcentral.com <co...@ringcentral.com> #8May 29, 2023 03:04AM

Thanks for reporting this issue.

COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.

Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.

sa...@gmail.com <sa...@gmail.com> #9Jun 28, 2023 06:59AM

We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.

Message last modified on Jun 28, 2023 07:03AM

aa...@gmail.com <aa...@gmail.com> #10Jul 5, 2023 02:02AM

Thank you very much! it is very useful to me . It solved my confusion.

nl...@163.com <nl...@163.com> #11Jul 5, 2023 02:09AM

I also encountered this problem, any updates for this?

co...@gmail.com <co...@gmail.com> #12Oct 16, 2023 08:11AM

hello, Luke, any updates for this issue?

lu...@google.com <lu...@google.com> Oct 26, 2023 01:07PM

Reassigned to am...@google.com.

am...@google.com <am...@google.com> #13Oct 26, 2023 02:12PM

This seems to be broken in debug as well in 8.3

am...@google.com <am...@google.com> #14Oct 27, 2023 05:43PM

Marked as fixed.

A fix has been merged which is expected to land in AGP 8.3-alpha12.

By the way, if you want jacoco to instrument your release apk, you also have to set android.testBuildType = 'release'

an...@google.com <an...@google.com> #15Nov 2, 2023 09:04PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Iguana | 2023.2.1 Canary 12
Android Gradle Plugin 8.3.0-alpha12

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

co...@gmail.com <co...@gmail.com> #16Nov 28, 2023 01:19AM

Thank you. Now the release package can be instrumented normally after testBuildType 'release' is set, but can you describe the correct configuration of testBuildType? Once testBuildType 'release' is set, the debug package will also be affected? As a result, the debug package instrument does not take effect.

co...@gmail.com <co...@gmail.com> #17Nov 30, 2023 01:05AM

I have met another problem, I created a new problem, please help to check, thanks.

https://issuetracker.google.com/issues/313968919

hy...@foxmail.com <hy...@foxmail.com> #18Jan 25, 2024 12:16PM

I use AGP 8.3.0-beta02 when isMinifyEnabled=true is set ,other library module jacoco instrument does not take effect app.build

buildTypes {
        release {
            isMinifyEnabled = true
            proguardFiles("proguard-rules/release.pro")
            enableAndroidTestCoverage = true
           }
}

other module

    buildTypes {
        release {
            isMinifyEnabled = false
            enableAndroidTestCoverage=true
            proguardFiles(getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro")
        }
....
}

cu...@gmail.com <cu...@gmail.com> #19Mar 6, 2024 12:44PM

this issue also exists when use AGP 7.4.2, is there any workaround to fix it under AGP 7.4.2?

di...@gmail.com <di...@gmail.com> #20May 31, 2024 07:56AM

I have a question：why enableAndroidTestCoverage does not work when isMinifyEnabled=true in AGP7.4.2
create(BuildTypes.JACOCO).apply {
```
isMinifyEnabled = true
testCoverage {
enableAndroidTestCoverage = true
enableUnitTestCoverage = true
}
```
}

ho...@hotmail.com <ho...@hotmail.com> #21Sep 4, 2024 09:50AM

Is there any way to make isMinifyEnabled(true) and jacoco work together?

ho...@hotmail.com <ho...@hotmail.com> #22Sep 13, 2024 03:02AM

Not work with AS(2023.2.1 Canary 12) + AGP (8.3.0-alpha12), any one tried?

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Iguana | 2023.2.1 Canary 12
Android Gradle Plugin 8.3.0-alpha12

Message last modified on Sep 13, 2024 03:02AM