-1

I'm basically following the migration guide from within Crashlytics (which is pretty much summarized in this post).

I followed the same instructions verbatim, you can see that from my git diff:

enter image description here

enter image description here

Yet when I sync my Gradle, I get this error:

5:02 PM Gradle sync failed: Could not find method compile() for arguments [com.google.firebase:firebase-core:11.4.2] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

Update

As mentioned in the comments (and as experienced by us at the end), we shouldn't migrate anyway until further notice:

enter image description here

Update 2

In fabric, if you click on Crashlytics, there is a link on the left nav bar that says Firebase, when you click on it you get this ad

enter image description here

halfer
  • 19,824
  • 17
  • 99
  • 186
abbood
  • 23,101
  • 16
  • 132
  • 246
  • Quick note - if you're currently using Fabric Crashlytics in your app we're recommending that you continue using it instead of migrating to Firebase Crashlytics right now. In the coming months, we'll have a migration path to easily move your apps to Firebase Crashlytics. – Alexizamerican Dec 15 '17 at 14:21
  • @Alexizamerican yeah figured.. see update to question. Please remove that invitation to migrate over to fabric from crashlytics in that case.. it's simply misleading – abbood Dec 15 '17 at 14:33
  • Thanks for the feedback. Can you let me know where you're seeing the invitation? I can work with the team to make it less confusing. – Alexizamerican Dec 15 '17 at 14:38
  • @Alexizamerican updated answer again – abbood Dec 15 '17 at 19:23
  • Thanks - I can see why that's confusing and I'll definitely share with the team. Appreciate the feedback! – Alexizamerican Dec 16 '17 at 05:00
  • @abbood: please do not beg for votes here. – halfer Jan 11 '18 at 19:15
  • (The reason is that we want votes to be authentic and organic, rather than skewed by social contract or obligation). – halfer Jan 11 '18 at 19:21

4 Answers4

1

The buildscript block is not a place for your application level dependencies. See this answer for more information on the buildscript block.

You need to place your compile or implementation/api(for gradle 3.4+ and android gradle plugin 3.0+) dependencies into the separate dependencies{} block with the rest of your dependencies, that is usually on the same level as your android plugin configuration.

Be_Negative
  • 4,892
  • 1
  • 30
  • 33
0
  • In your project level grade file, you need to add, maven { url 'https://maven.fabric.io/public' } to the repositories.

  • add the following to your dependencies classpath 'io.fabric.tools:gradle:1.25.1''

  • In your app level Gradle file put apply plugin: 'io.fabric' below apply plugin: 'com.android.application' and under depencies place this implementation('com.crashlytics.sdk.android:crashlytics:2.7.1@aar') { transitive = true }

  • place apply plugin:'com.google.gms.google-services' at the bottom of the app level gradle file.
mhdtouban
  • 851
  • 2
  • 11
  • 20
0

Change compile '...' to implementation '...'

Saran Sankaran
  • 2,335
  • 2
  • 19
  • 34
0

You are using Google Services plugin 3.0.0. The instructions for adding the Crashlytics SDK indicate that 3.1.2 or higher is required:

Note: Crashlytics requires Google Services plugin version 3.1.2 or higher. Check the com.google.gms:google-services version number in your project's build.gradle dependencies.

Bob Snyder
  • 37,759
  • 6
  • 111
  • 158