Please reduce/remove info-level logging for AGP "Analytics other plugin to proto: ..." [300502151]

Fixed

Bug

Status Update

No update yet.

Description

mc...@ebay.com

created issue #1

Sep 14, 2023 10:54PM

AGP has --info level logging which produces an excessive amount of content on our project.

com.android.build.gradle.internal.profile.AnalyticsUtil#otherPluginToProto

It would seem that for every plugin on every project module it logs to Gradle at the --info level a message like the following for every plugin that it doesn't know:

Analytics other plugin to proto: Unknown plugin type com.example.Plugin expected enum COM_EXAMPLE_PLUGIN

On a large project such as ours with over 600 project modules and a large number of applied convention plugins that ends up dumping 23069 lines into the info-level log, which is surprisingly even more than the remainder of all logging in the log file (21319 lines).

Please move this to debug level logging (already useless in Gradle logs) or remove it altogether.

Studio Build: N/A Version of Gradle Plugin: 8.1.1 Version of Gradle: Gradle 8.3 Version of Java: 17.0.6 (Azul Systems, Inc. 17.0.6+10-LTS) OS: Mac OS X 13.5.2 aarch64

Comments

ra...@google.com <ra...@google.com> Sep 15, 2023 04:28PM

Assigned to an...@google.com.

je...@google.com <je...@google.com> #2Sep 18, 2023 05:05PM

Reassigned to cm...@google.com.

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?

cm...@google.com <cm...@google.com> Sep 18, 2023 05:30PM

Accepted by cm...@google.com.

cm...@google.com <cm...@google.com> #3Sep 19, 2023 12:01PM

Marked as fixed.

the fractional part of the location data is exactly the same.

mc...@ebay.com <mc...@ebay.com> #4Sep 19, 2023 09:47PM

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.

an...@google.com <an...@google.com> #5Sep 21, 2023 09:04PM

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

mc...@ebay.com <mc...@ebay.com> #6Sep 21, 2023 11:41PM

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