大佬教程收集整理的这篇文章主要介绍了无法使用 Android Studio 4.2 将 Gradle 与 Firebase Crashlytic 2.6.0 同步，大佬教程大佬觉得挺不错的，现在分享给大家，也给大家做个参考。
项目级 build.gradle
buildscript {
addRepos(repositorIEs)
dependencIEs {
classpath 'com.Google.gms:Google-services:4.3.5'
// Crashlytic
classpath 'com.Google.firebase:firebase-crashlytics-gradle:2.6.0'
}
}
应用级 build.gradle
apply plugin: 'com.androID.application'
apply plugin: 'kotlin-androID'
apply plugin: 'kotlin-android-extensions'
apply plugin: 'kotlin-kapt'
apply plugin: 'com.Google.gms.Google-services'
apply plugin: 'com.Google.firebase.crashlytics'
dependencIEs {
// Crashlytic
implementation 'com.Google.firebase:firebase-crashlytics:18.0.0'
}
使用 gradle 4.3.5 和 Firebase crashlytic 2.6.0 我的应用程序停止编译并出现以下错误
class org.gradle.API.internal.file.DefaultfilePropertyFactory$DefaultDirectoryVar$2 cAnnot be cast to class org.gradle.API.file.Directory (org.gradle.API.internal.file.DefaultfilePropertyFactory$DefaultDirectoryVar$2 and org.gradle.API.file.Directory are in unnamed module of loader org.gradle.internal.classloader.Visitableurlclassloader @68be2bc2)
class org.gradle.API.internal.file.DefaultfilePropertyFactory$DefaultDirectoryVar$2 cAnnot be cast to class org.gradle.API.file.Directory (org.gradle.API.internal.file.DefaultfilePropertyFactory$DefaultDirectoryVar$2 and org.gradle.API.file.Directory are in unnamed module of loader org.gradle.internal.classloader.Visitableurlclassloader @68be2bc2)
Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.)
Re-download dependencIEs and sync project (requires network)
The state of a Gradle build process (daemon) may be corrupt. StopPing all Gradle daemons may solve this problem.
Stop Gradle build processes (requires restart)
Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project.
In the case of corrupt Gradle processes,you can also try closing the IDE and then killing all Java processes.
但是如果我将 Firebase crashlytic 版本更改为 2.3.0 一切正常
你们知道为什么会这样吗？
我遇到了完全相同的问题。似乎最新的 crashlytics-gradle 插件与某些东西不兼容。使用较低版本的 crashlytics-gradle 插件有所帮助。而不是 firebase-crashlytics-gradle:2.6.0 尝试使用这个版本：
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.4.1'
这对我有用......如果这对你不起作用，你可以尝试更低的版本。可以在此处找到版本列表：
https://firebase.google.com/support/release-notes/android#crashlytics_gradle_plugin_v2-0-0
当您搜索“Crashlytics Gradle 插件版本”时，您可以看到所有已发布的 Crashlytics Gradle 插件版本。
更新：
我还必须将应用级别 build.gradle 中的 compiLeoptions 更改为：
compiLeoptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
当目标和源兼容性未设置为 1_8 时，项目已编译但在尝试运行应用程序时崩溃：
--------- beginning of crash
2021-06-09 17:22:28.765 29519-29519/com.resmed.myair.cpl E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.resmed.myair.cpl,PID: 29519
java.lang.bootstrapMethodError: Exception from call site #45 bootstrap method
at com.google.firebase.components.ComponentDiscovery.discoverLazy(ComponentDiscovery.java:112)
at com.google.firebase.FirebaseApp.<init>(FirebaseApp.java:418)
at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:299)
at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:267)
at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:252)
at com.google.firebase.provider.FirebaseInitProvider.onCreate(FirebaseInitProvider.java:51)
at android.content.ContentProvider.attachInfo(ContentProvider.java:1917)
at android.content.ContentProvider.attachInfo(ContentProvider.java:1892)
at com.google.firebase.provider.FirebaseInitProvider.attachInfo(FirebaseInitProvider.java:45)
at android.app.ActivityThread.installProvider(ActivityThread.java:6239)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:5805)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5722)
at android.app.ActivityThread.-wrap1(Unknown source:0)
at android.app.ActivityThread$H.handlemessage(ActivityThread.java:1656)
at android.os.Handler.dispatchmessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
Caused by: java.lang.NoClassDefFoundError: Invalid descriptor: minimize.
at com.google.firebase.components.ComponentDiscovery.discoverLazy(ComponentDiscovery.java:112)
at com.google.firebase.FirebaseApp.<init>(FirebaseApp.java:418)
at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:299)
at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:267)
at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:252)
at com.google.firebase.provider.FirebaseInitProvider.onCreate(FirebaseInitProvider.java:51)
at android.content.ContentProvider.attachInfo(ContentProvider.java:1917)
at android.content.ContentProvider.attachInfo(ContentProvider.java:1892)
at com.google.firebase.provider.FirebaseInitProvider.attachInfo(FirebaseInitProvider.java:45)
at android.app.ActivityThread.installProvider(ActivityThread.java:6239)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:5805)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5722)
at android.app.ActivityThread.-wrap1(Unknown source:0)
at android.app.ActivityThread$H.handlemessage(ActivityThread.java:1656)
at android.os.Handler.dispatchmessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
以上是大佬教程为你收集整理的无法使用 Android Studio 4.2 将 Gradle 与 Firebase Crashlytic 2.6.0 同步全部内容，希望文章能够帮你解决无法使用 Android Studio 4.2 将 Gradle 与 Firebase Crashlytic 2.6.0 同步所遇到的程序开发问题。
如果觉得大佬教程网站内容还不错，欢迎将大佬教程推荐给程序员好友。
本图文内容来源于网友网络收集整理提供，作为学习参考使用，版权属于原作者。
如您有任何意见或建议可联系处理。小编QQ：384754419，请注明来意。