Fabric crashes after the update : [Fabric isCrashlyticsCollectionEnabled]: unrecognized selector sent to class 0x10c0bb918

匿名 (未验证) 提交于 2019-12-03 01:38:01

问题:

Today fabric crashes after the pod update

Fabric 1.9.0

[Fabric isCrashlyticsCollectionEnabled]: unrecognized selector sent to class 0x10c0bb918 

Crashing line :

Fabric.with([Crashlytics.self]) 

It crashes at app startup. Anyone having the same problem?

回答1:

I reverted to a previous version of Crashlytics by updating my Podfile

pod 'Fabric', '1.8' pod 'Crashlytics', '3.11' 

Then updating Cocoapods:

pod update 'Crashlytics'

Hopefully Google fixes this soon



回答2:

  1. Go to the "Update via Manual Steps" and download the zip file. Here is the link: https://fabric.io/kits/ios/crashlytics/update?type=manual

  2. Unzip, copy and replace the frameworks (Fabric and Crashlytics)

It worked for me



回答3:

This is probably caused by that fact that Fabric SDK's version is incompatible with Crashlytics SDK's version. I happened to stumble on this pitfall when I ran 'pod update Fabric'.

This updated the Fabric SDK but not the Crashlytics. And the problem occurred.

However, Crashlytics SDK's podspec file specifies a dependency on Fabric and also the compatible versions of this dependency. This is what I assumed from the Podfile.lock file:

   - Crashlytics (3.8.6):      - Fabric (~> 1.6.3) 

So, if the version range specification '(~> 1.6.3)' is correct, even though I ran 'pod update Fabric', this problem shouldn't occur. However, it did. So, my conclusion is the version range specification contains incompatible versions.

My solution is to run 'pod update Crashlytics' only and updated the Crashlytics and also its dependencies.

If this doesn't solve your problem, try removing Fabric and Crashlytics and adding the latest version back.



易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!