Menu
Getting the following errors after applying proguard rules:
Could not find method create() for arguments [crashlyticsStoreDeobsRelease, class com.crashlytics.tools.gradle.tasks.StoreMappingFileTask, com.android.build.gradle.internal.scope.BuildArtifactsHolder$FinalBuildableArtifact@1711854a] on task set of type org.gradle.api.internal.tasks.DefaultTaskContainer.
338
Alternatively, you can continue using the legacy Fabric Crashlytics plugin if you downgrade to the older Android Gradle plugin. Sorry, something went wrong. I'm sorry, seems like I looked at the wrong component, apparently I was using Fabric Crashlytics plugin version 1.28.0!
Changes in Android Gradle plugin 4.0 can trigger a race condition in Gradle when running with --no-daemon and versions of Gradle 6.3 or lower, causing builds to hang after the build is finished. This issue will be fixed in Gradle 6.4. This version of the Android plugin requires the following: Gradle 5.6.4 .
With this update, you no longer need to specify a version for the SDK Build Tools. The Android Gradle plugin now uses version 28.0.3 by default.
This appears to be an issue with our plugin and the newest released version of the Android Gradle plugin; looks like the stacktrace passes through Crashlytics here: at com.crashlytics.tools.gradle.CrashlyticsPlugin.createTaskBuilder (CrashlyticsPlugin.groovy:301) Have you migrated to Firebase?
It looks like the version of fabric build tools in your build.gradle is set to something like classpath 'io.fabric.tools:gradle:+' which means it always uses the newest available version.
The current version 1.26.0 seems broken so you can temporarily set exact version to 1.25.4: classpath 'io.fabric.tools:gradle:1.25.4'.
Checked a couple of minutes ago, it works.
UPD: new version io.fabric.tools(1.26.1) is released. classpath 'io.fabric.tools:gradle:+' now works well
155
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
