AGP 8.4 tries to set up Startup Profiles on debug builds [339313346]

Fixed

Bug

Status Update

No update yet.

Description

ma...@whatnot.com

created issue #1

May 8, 2024 12:52PM

DESCRIBE THE ISSUE IN DETAIL:

It seems like combining AGP 8.4 with Startup Profiles results in a ton of Startup method not found: XYZ log messages being spit out when building a debug app from a command line.

Command: ./gradlew assembleDebug

...
Startup method not found: void events.OnboardingOptionTap$Companion$defaultInstance$2.<clinit>()
Startup method not found: void events.OnboardingOptionTap$Companion$defaultInstance$2.<init>()
Startup method not found: void events.OnboardingOptionTap$Companion$descriptor$2.<clinit>()
Startup method not found: void events.OnboardingOptionTap$Companion$descriptor$2.<init>()
Startup method not found: void events.OnboardingOptionTap$Companion.<init>()
...

Logging process takes so long that I feel like the entire profile might be printed out. The build passes fine. Just thousands of lines printed out.

The build itself finishes with, indicating that it tried to work it out even if it's a debug build:

WARNING: D8: Unable to include all startup classes in classes.dex. 
Startup classes were distributed in: classes.dex, classes2.dex, classes3.dex.

I wonder if this is somehow related to this changelog mentioned in the Baseline Profile 8.4 docs:

Local app installations of non-debuggable builds using the Gradle wrapper command line tool or Android Studio install Baseline Profiles, so the performance of your local release build more closely matches production. 
This update doesn't affect production performance of Baseline Profiles.

IMPORTANT: Please read https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Studio Build: unrelated Version of Gradle Plugin: 8.4.0 Version of Gradle: 8.7 Version of Java: 17 OS: MacOS

Comments

aa...@google.com <aa...@google.com> May 9, 2024 12:40PM

Assigned to an...@google.com.

sg...@google.com <sg...@google.com> #2May 13, 2024 01:55PM

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?

je...@google.com <je...@google.com> May 13, 2024 04:22PM

Reassigned to cc...@google.com.

cc...@google.com <cc...@google.com> #3May 13, 2024 04:56PM

Reassigned to je...@google.com.

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

ma...@whatnot.com <ma...@whatnot.com> #4May 13, 2024 05:01PM

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.

ma...@whatnot.com <ma...@whatnot.com> #5May 13, 2024 05:05PM

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

je...@google.com <je...@google.com> May 13, 2024 05:28PM

Reassigned to mi...@google.com.

ma...@google.com <ma...@google.com> #6May 13, 2024 06:29PM

Reassigned to mi...@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

ma...@whatnot.com <ma...@whatnot.com> #7May 14, 2024 08:22AM

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

be...@google.com <be...@google.com> #8May 14, 2024 08:34AM

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.

ma...@whatnot.com <ma...@whatnot.com> #9May 14, 2024 09:21AM

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.

ma...@google.com <ma...@google.com> #10May 14, 2024 04:10PM

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

mi...@google.com <mi...@google.com> #11May 20, 2024 10:35PM

Marked as fixed.

A fix for this has been submitted, which removes the startup profile tasks from being run for debug builds.

an...@google.com <an...@google.com> #12May 23, 2024 11:13PM

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 Koala Feature Drop | 2024.1.2 Canary 3
Android Gradle Plugin 8.6.0-alpha03

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!

wb...@gmail.com <wb...@gmail.com> #13May 24, 2024 08:36AM

Will the fix also be backported to AGP 8.4.x ?

mi...@google.com <mi...@google.com> #14May 24, 2024 11:21AM

There are no current plans to backport this change.