Menu
I am working in an iOS Library and I want to add Crashlytics so I can get notified if the library crashes to any user. I have already integrated the Crashlytics and Fabric frameworks: I added the .frameworks bundles, then I added the Fabric API Key into the library's info.plist as well as the run script phase into build phases, but when the library crashes inside a running app, nothing happens in the fabric dashboard.
Is it possible to add Crashlytics to an iOS Library?
214
Implementation path. Start by adding Firebase to your app in the Firebase console. Add the Crashlytics SDK via CocoaPods, Gradle, or Pub, and Crashlytics starts collecting reports. Visit the Firebase console to track, prioritize, and fix issues in your app.
Old versions of your app still using the Fabric Crashlytics SDK will not break once it's deprecated, however they will no longer submit crash reports. But it seems like it will just continue to work as per normal after this date until further notice.
Looks like the answer is technically "YES", but it would be a bad idea to do so.
Mike Bonnell's comments in another post:
Comment 1:
Mike from Fabric here. If you're planning on distributing this framework to third parties, do not include Fabric or Crashlytics in it.
Comment 2:
Sure, our SDK only supports being initialized once. Being initialized in a framework and application would cause a conflict. You and the app developer would have different API keys and there is no way to ask the app developer to give permission to your SDK to share stack traces from their code with your framework. Including us in your framework will cause issues for your framework and anyone that uses it, so that's why I said don't include us! Totally understand that SDK developers would love to see this supported.
169
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
