Unable to get provider com.crashlytics.android.CrashlyticsInitProvider

After implementation 'com.google.firebase:firebase-core:16.0.1' and classpath 'com.google.gms:google-services:4.0.1'

在实施'com.google.firebase:firebase-core:16.0.1'和classpath'com.google.gms:google-services:4.0.1'之后

I started getting the following error when starting the application:

启动应用程序时,我开始收到以下错误:

FATAL EXCEPTION: main Process: com.fentury.android, PID: 10771 java.lang.RuntimeException: Unable to get provider com.crashlytics.android.CrashlyticsInitProvider: io.fabric.sdk.android.services.concurrency.UnmetDependencyException: This app relies on Crashlytics. Please sign up for access at https://fabric.io/sign_up, install an Android build tool and ask a team member to invite you to this app's organization. at android.app.ActivityThread.installProvider(ActivityThread.java:5856) at android.app.ActivityThread.installContentProviders(ActivityThread.java:5445) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5384) at android.app.ActivityThread.-wrap2(ActivityThread.java) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1545) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:154) at android.app.ActivityThread.main(ActivityThread.java:6119) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776) Caused by: io.fabric.sdk.android.services.concurrency.UnmetDependencyException: This app relies on Crashlytics. Please sign up for access at https://fabric.io/sign_up, install an Android build tool and ask a team member to invite you to this app's organization. at com.crashlytics.android.core.CrashlyticsCore.onPreExecute(CrashlyticsCore.java:235) at com.crashlytics.android.core.CrashlyticsCore.onPreExecute(CrashlyticsCore.java:209) at io.fabric.sdk.android.InitializationTask.onPreExecute(InitializationTask.java:44) at io.fabric.sdk.android.services.concurrency.AsyncTask.executeOnExecutor(AsyncTask.java:611) at io.fabric.sdk.android.services.concurrency.PriorityAsyncTask.executeOnExecutor(PriorityAsyncTask.java:43) at io.fabric.sdk.android.Kit.initialize(Kit.java:69) at io.fabric.sdk.android.Fabric.initializeKits(Fabric.java:440) at io.fabric.sdk.android.Fabric.init(Fabric.java:384) at io.fabric.sdk.android.Fabric.setFabric(Fabric.java:342) at io.fabric.sdk.android.Fabric.with(Fabric.java:313) at com.crashlytics.android.CrashlyticsInitProvider.onCreate(CrashlyticsInitProvider.java:27) at android.content.ContentProvider.attachInfo(ContentProvider.java:1751) at android.content.ContentProvider.attachInfo(ContentProvider.java:1726) at android.app.ActivityThread.installProvider(ActivityThread.java:5853) ... 10 more

致命异常:主要进程:com.fentury.android,PID:10771 java.lang.RuntimeException:无法获取提供者com.crashlytics.android.CrashlyticsInitProvider:io.fabric.sdk.android.services.concurrency.UnmetDependencyException:此应用程序依赖在Crashlytics上。请通过https://fabric.io/sign_up注册访问,安装Android构建工具并要求团队成员邀请您加入此应用的组织。在android.app.ActivityThread.installProviders(ActivityThread.java:5445)的android.app.ActivityThread.installProvider(ActivityThread.java:5856)安卓android.app.ActivityThread.handleBindApplication(ActivityThread.java:5384)。 Activity.Thread.- wrap2(ActivityThread.java)位于Android.os.Looper.loop上android.app.Handler.dispatchMessage(Handler.java:102)的android.app.ActivityThread $ H.handleMessage(ActivityThread.java:1545) Looper.java:154)在android.app.ActivityThread.main(ActivityThread.java:6119)at java.lang.reflect.Method.invoke(Native Method)at com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run( ZygoteInit.java:886)在com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)引起:io.fabric.sdk.android.services.concurrency.UnmetDependencyException:这个应用程序依赖于Crashlytics。请通过https://fabric.io/sign_up注册访问,安装Android构建工具并要求团队成员邀请您加入此应用的组织。 at com.crashlytics.android.core.CrashlyticsCore.onPreExecute(CrashlyticsCore.java:235)at com.crashlytics.android.core.CrashlyticsCore.onPreExecute(CrashlyticsCore.java:209)at io.fabric.sdk.android.InitializationTask.onPreExecute (InitializationTask.java:44)at io.fabric.sdk.android.services.concurrency.AsyncTask.executeOnExecutor(AsyncTask.java:611)at io.fabric.sdk.android.services.concurrency.PriorityAsyncTask.executeOnExecutor(PriorityAsyncTask.java) :43)io.fabric.sdk.android.Kit.initialize(Kit.java:69)at io.fabric.sdk.android.Fabric.initializeKits(Fabric.java:440)at io.fabric.sdk.android。 Fabric.init(Fabric.java:384)在io.fabric.sdk.android.Fabric.setFabric(Fabric.java:342)at io.fabric.sdk.android.Fabric.with(Fabric.java:313)at com .crashlytics.android.CrashlyticsInitProvider.onCreate(CrashlyticsInitProvider.java:27)位于android.app的android.content.ContentProvider.attachInfo(ContentProvider.java:1751)android.content.ContentProvider.attachInfo(ContentProvider.java:1726)。 ActivityThread.installProvider(ActivityThread.java:5853)......还有10个

Also added in AndroidManifest.xml next line:

AndroidManifest.xml中还添加了下一行:

<meta-data android:name="firebase_crash_collection_enabled" android:value="false" />

3 个解决方案

#1

If you are going to use other Firebase's API's, I'd suggest to setup crashlytics
As mentioned on Firebase's crashlytics page, here.

如果您打算使用其他Firebase的API,我建议设置crashlytics如Firebase的crashlytics页面所述。

And obviously before that you'd need to setup firebase for your app
and create project through firebase console.
I believe you had already done that.

显然在此之前,您需要为您的应用设置firebase并通过firebase控制台创建项目。我相信你已经做到了。

It's because I see small difference in crashlytics setup on these two pages(fabric and firebase).
like on firebase's crashlytics:
in app level gradle

这是因为我发现这两个页面(结构和firebase)上的碰撞设置有很小的不同。就像在firebase的崩溃问题上一样:在app level gradle中

dependencies {
    // ...
    implementation 'com.crashlytics.sdk.android:crashlytics:2.9.3'
}

on fabric:

dependencies {
    // ...
      implementation('com.crashlytics.sdk.android:crashlytics:2.9.4@aar') {
    transitive = true;
  }
}

You won't need to add fabric api key through manifest if you are using with firebase, I think it somehow get connected with firebase key(just guessing).
I'm saying this from my experience, anyone correct me if I'm somewhere wrong.

如果你使用firebase,你将不需要通过清单添加fabric api密钥,我认为它以某种方式与firebase密钥连接(只是猜测)。我是根据我的经验说的,如果我出错了,任何人都会纠正我。

3 个解决方案

#1

更多相关文章

随机推荐