IssueTracker

Sample project attached.

I attached a project in comment #2. Build this project and deploy to any API 35 device.

Run the app once to allow the BroadcastReceiver to register. Then rerun it over and over again.

On any API 35 device (I used an emulator and a Pixel 8 Pro), the BroadcastReceiver will get BOOT_COMPLETED action every time you launch the app.

This seems to only happen when launching the app from Android Studio. When I force stop the app and launch it from the device itself, it doesn't happen. Something about the way AS launches the device is triggering the BOOT_COMPLETED event. But only on API 35

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

I'm just now experiencing that something is not right. Regarding 2 types of intent event.

• android.intent.action.BOOT_COMPLETED
• android.intent.action.LOCKED_BOOT_COMPLETED

I also experience this when I launch the app from Android Studio. But I also get additional log.

• BOOT_COMPLETED_BROADCAST_COMPLETION_LATENCY_REPORTED action:android.intent.action.LOCKED_BOOT_COMPLETED dispatchLatency:1 completeLatency:604 dispatchRealLatency:0 completeRealLatency:604 receiversSize:1 userId:0 userType:android.os.usertype.full.SYSTEM
• BOOT_COMPLETED_BROADCAST_COMPLETION_LATENCY_REPORTED action:android.intent.action.BOOT_COMPLETED dispatchLatency:604 completeLatency:837 dispatchRealLatency:604 completeRealLatency:837 receiversSize:2 userId:0 userType:android.os.usertype.full.SYSTEM

• Device: S25 Ultra android 15
• Android Studio: 2024.2.2 Patch 1

There should be one dump file per D8/R8 compilation. If your app depends on multiple modules and some of these are maybe built using D8, then there could be many dumps.

The dump for the R8 compilation can usually be identified by the fact that this dump has a higher timestamp than other dumps, is bigger than most other dumps, and has a proguard.config file in the dump.

You can share it privately with christofferqa@google.com and sgjesse@google.com.

That will be 3.0.72.

The recommended way to use a different version of R8 is to add the following to your settings.gradle or settings.gradle.kts;

pluginManagement {
   buildscript {
       repositories {
           mavenCentral()
           maven {
               url = uri("https://storage.googleapis.com/r8-releases/raw")
           }
       }
       dependencies {
           classpath("com.android.tools:r8:3.0.72")  // <-- R8 version 3.0.72
           classpath('com.google.guava:guava:30.1.1-jre')  // <-- THIS IS REQUIRED UNTIL R8 3.2.4-dev
       }
   }
}

For the record, this was due to the app searching for the first instance in a list that satisfied that x.getClass().getCanonicalName() == someCanonicalName. In the original program, the instances were all of different class types, but after horizontal class merging, some of the instances ended up having the same class type, leading to different program behavior.

The suggested fix is to rewrite the predicate in way that does not use reflection (getCanonicalName()) or add a keep rule:

-keep,allowobfuscation,allowshrinking class * extends AbstractBaseClass