IssueTracker

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