Ndtyjky

When using Firebase Performance in Android Studio the gradle task app:transformClassesWithFirebasePerformancePluginForDebug is taking significantly longer than any other task and is therefore dramatically slowing down my gradle build times.

Slow Build shown in Profiler

Firebase in our project caused 40% build time increase. To speed up debug builds we added a possibility to switch it on/off using build parameters in app/build.gradle and root build.gradle files:

app:

if (!project.hasProperty("disable-performance-plugin")) {
apply plugin: 'com.google.firebase.firebase-perf' }

root/buildscript/dependencies:

if (!project.hasProperty("disable-performance-plugin")) {
classpath('com.google.firebase:firebase-plugins:1.1.5') {
exclude group: 'com.google.guava', module: 'guava-jdk5'
}
}

when running from the command line use

./gradlew your-task -Pdisable-performance-plugin

when working from Android Studio, add the flag to compiler options:

All of the existing answers are valid, but they all miss something.

To deal with this issue, you have 2 major options to choose from.

1. Use firebasePerformanceInstrumentationEnabled property

This is the official way provided by the SDK itself to disable it during the build process.

What this does:

• Reduces transformClassesWithFirebasePerformancePluginFor* task execution time to ~5-10s.


• Disables automatic traces and request monitoring, but leaves custom traces enabled. You can control the latter with AndroidManifest <meta-data> tags and calls to FirebasePerformance.getInstance().setPerformanceCollectionEnabled(). More info in the docs.

Pros:

• Only one property to set up.

Cons:

• Doesn't disable performance monitoring completely (if that's what you want).


• Plugin still adds additional ~5-15s to the build time.

How to do this:

I think it's much easier to only enable plugin in those rare cases when we need it (usually it will be only when we publish the app), rather than disable it in all other cases.
Note: Of course, with manual builds you might forget to enable it. So if you don't have CI, maybe it's worth adding some other automatic scripting in Gradle, or sticking to the opposite approach that is used in other answers.

In general though, we only need two steps:

1. 
   

   Add the following line to gradle.properties file:

   
   
   

   firebasePerformanceInstrumentationEnabled=false
   
   

   
   


2. 
   

   Use the following command in your CI config or manual builds:

   
   
   

   
   

   ./gradlew assembleRelease -PfirebasePerformanceInstrumentationEnabled=true

   
   

   
   

2. Use custom Gradle project property to avoid applying firebase-perf Gradle plugin

What this does:

• Completely removes transformClassesWithFirebasePerformancePluginFor* task and also some additional ~5-10s overhead that is present when using the first solution.


• Same as the first method – disables automatic traces and request monitoring, but leaves custom traces enabled. You can control the latter with AndroidManifest <meta-data> tags and calls to FirebasePerformance.getInstance().setPerformanceCollectionEnabled(). More info in the docs.

Pros:

• 
  Completely eliminates time expenses associated with Firebase Performance Gradle plugin.

Cons:

• Introduces conditional check for applying plugin in your Gradle script, some might argue that it's not an idiomatic approach.


• Again, doesn't disable performance monitoring completely (if that's what you want).

How to do this:

This approach has similar points and warnings, and also includes two steps:

1. 
   

   Modify your app module's build.gradle file:

   
   
   

   if (project.hasProperty('useFirebasePerf')) {
   
     apply plugin: 'com.google.firebase.firebase-perf'
   
   }
   
   

   
   
   

   Note: you don't need to apply the same check to your project-level build.gradle:

   
   
   

   classpath "com.google.firebase:firebase-plugins:$firebase_plugins_version"
   
   

   
   
   

   This declaration won't be used in any way by Gradle when the plugin itself is not enabled.

   
   
   

   And you don't need to exclude guava-jdk5 dependency there, if you're using firebase-plugins v1.1.1 or later as stated in the docs.

   
   


2. 
   

   Use the following command in your CI config or manual builds:

   
   
   

   
   

   ./gradlew assembleRelease -PuseFirebasePerf

   
   

   
   

3. (Additional) Use custom Gradle project property to exclude firebase-perf SDK

If you don't use custom traces or any other features from Firebase Performance SDK and only rely on automatic monitoring (that is, you don't have any dependencies on SDK in your code), then you can exclude this dependency for non-production builds.

Advantage:

• This might save you some additional ~5-10s, spent on configuring dependency and
  "ProGuarding" it.

Drawbacks:

• If you were carefully measuring your APK size, you will suddenly see an increase at about 0.4mb. This might disrupt your reports or predictions, so you need to be aware of it.


• Also, if you were close to surpassing 64K method count limit, you might suddenly step over it, see your build fail and find yourself in the MultiDex zone with the need to additionally implement it and test your application. All because Firebase Performance brings a formidable number of almost 5K method references (after applying ProGuard with optimizations).

How to do this:

All you need to do is update your app module's build.gradle file:

• 
  

  If you chose to use the first option, then change your dependency like this:

  
  
  

  if (project.property('firebasePerformanceInstrumentationEnabled') == 'true') {
  
    implementation "com.google.firebase:firebase-perf:${firebase_perf_version}"
  
  }
  
  

  
  


• 
  

  If you chose the second one:

  
  
  

  if (project.hasProperty('useFirebasePerf')) {
  
    implementation "com.google.firebase:firebase-perf:${firebase_perf_version}"
  
  }
  
  

  
  

Just to give another option to disable transformClassesWithFirebasePerformancePluginForDebug, here's my recipe:

In main build.gradle folder:

if (!project.gradle.startParameter.taskNames.any { taskName ->

     taskName.toLowerCase().contains('assemble') && taskName.toLowerCase().contains('debug') }) {

     classpath("com.google.firebase:firebase-plugins:$firebasePluginVersion") {

         exclude group: 'com.google.guava', module: 'guava-jdk5'

     }

}

In the build.gradle app file:

if (!project.gradle.startParameter.taskNames.any { taskName ->

    taskName.toLowerCase().contains('assemble') && taskName.toLowerCase().contains('debug') }) {

    apply plugin: 'com.google.firebase.firebase-perf'

}

I ran into this problem as well. Originally we had been using a variant of the answer provided by R. Zagórski, but based on a similar thread from the Gradle forums it seems like conditionally applying a plugin to a project isn't the right way to go:

Plugins can’t be applied to only “part of your project”. They are either applied or not.

Conditionally applying plugins does seem to work if you can do it right, but it's not an officially supported feature. Further down the same thread, another point is made:

But the plugin should allow you to configure it at a finer grained level.

Sure enough, there actually is a property exposed by the Firebase plugin that lets you toggle instrumentation on or off (therefore toggling the increased build time). Using this property is tricky, though, since you have to apply it at exactly the right time during the building process, but once you've got that then you can essentially pivot it on whatever you want.

The following code snippet is how we're pivoting instrumentation based on Debug vs. Non-Debug build variants. It's written in Kotlin, but I imagine it would translate to Groovy just as well:

plugins {

    ...

    id ("com.google.firebase.firebase-perf")

}



...



android {

    ...



    applicationVariants.all {

        val variant = this

        val isFirebaseEnabled = !variant.javaCompiler.name.contains("Debug", true)



        gradle.taskGraph.whenReady {

            if (this.hasTask(variant.javaCompiler))

            {

                project.FirebasePerformance.isInstrumentationEnabled = isFirebaseEnabled

            }

        }

    }



    ...

}

Note that with this in place, the transformClassesWithFirebasePerformancePluginFor* task will still always run for every build variant, but it will complete almost immediately for a variant that doesn't have instrumentation enabled.