Plugin with id 'com.google.firebase.firebase-perf' not found
Asked Answered
M

4

6

In implementing the 'Performance' feature of Firebase, I got the following error attempting to sync the Gradle:

Plugin with id 'com.google.firebase.firebase-perf' not found.

I implemented it following instructions here: https://firebase.google.com/docs/perf-mon/get-started-android. In particular it directs you to specify the classpath dependency to com.google.firebase:perf-plugin in your root-level (project-level) Gradle file, not he app-level:

enter image description here

Here are my Gradles, app-level left, project-level right:

enter image description here

Molly answered 11/10, 2020 at 15:55 Comment(1)
more than 1 year and the firebase-perf did not update or mentioned anything related to this issue. It is really something badElectrodynamometer
M
1

Despite the red box warning not to put the perf-plugin in the app-level Gradle, putting it there allowed syncing and compiling, but with all sorts of new red warnings in the compile build log:

enter image description here

enter image description here

Not including the plugin at all still gave me something in my performance tab a couple weeks after adding just the implementation line:

implementation 'com.google.firebase:firebase-perf:19.0.9'

enter image description here

The better of these two Performance implementation solutions, to just leave the plugin out vs the gains of adding it to the app-level Gradle, despite apparent dependency conflict risks and build exceptions, I'd be open to views.

Molly answered 11/10, 2020 at 15:55 Comment(1)
If you don't add the plugin, then it won't do automatic monitoring of HTTP requests as advertised. So, that's not exactly a "fix". If you have a problem with the plugin, you should report that to Firebase support directly. support.google.com/firebase/contact/supportKeewatin
J
8

Please add Performance plugin in your dependency class-path

`classpath 'com.google.firebase:perf-plugin:1.3.1'  // Performance Monitoring plugin`
Joviality answered 23/12, 2020 at 6:29 Comment(0)
G
8

Try this

id 'com.google.firebase.firebase-perf' version '1.4.2' apply false
Gasworks answered 30/3, 2023 at 3:14 Comment(2)
Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.Bettyannbettye
This was helpful for me! Why would it change name when using .kts??Moir
C
3

The configurations Firebase gave us to do are the following:

App Gradle: enter image description here Project Gradle: enter image description here

Solution to fix the problem:

  1. Remove id("com.google.firebase.firebase-perf") from plugins section in Project Gradle.
  2. Instead, add classpath("com.google.firebase:perf-plugin:1.4.2") to buildscript/dependencies in Project Gradle, like below:

enter image description here

Cedrickceevah answered 9/1 at 17:51 Comment(0)
M
1

Despite the red box warning not to put the perf-plugin in the app-level Gradle, putting it there allowed syncing and compiling, but with all sorts of new red warnings in the compile build log:

enter image description here

enter image description here

Not including the plugin at all still gave me something in my performance tab a couple weeks after adding just the implementation line:

implementation 'com.google.firebase:firebase-perf:19.0.9'

enter image description here

The better of these two Performance implementation solutions, to just leave the plugin out vs the gains of adding it to the app-level Gradle, despite apparent dependency conflict risks and build exceptions, I'd be open to views.

Molly answered 11/10, 2020 at 15:55 Comment(1)
If you don't add the plugin, then it won't do automatic monitoring of HTTP requests as advertised. So, that's not exactly a "fix". If you have a problem with the plugin, you should report that to Firebase support directly. support.google.com/firebase/contact/supportKeewatin

© 2022 - 2024 — McMap. All rights reserved.