应用安装Firebase Crashlytics的依赖关系咨询
Hey folks, let's break down the dependency tree for com.crashlytics.sdk.android:crashlytics:2.9.1—since your team's planning to integrate this Firebase-linked component, it's helpful to map out exactly what it pulls into your project:
--- com.crashlytics.sdk.android:crashlytics:2.9.1 +--- io.fabric.sdk.android:fabric:1.4.2 +--- com.crashlytics.sdk.android:beta:1.2.7 | \--- io.fabric.sdk.android:fabric:1.4.1 -> 1.4.2 +--- com.crashlytics.sdk.android:answers:1.4.1 | \--- io.fabric.sdk.android:fabric:1.4.1 -> 1.4.2
A quick heads-up: you’ll notice the beta and answers sub-modules originally reference Fabric 1.4.1, but your build tool (like Gradle) is automatically resolving that to the newer 1.4.2 version used by the main Crashlytics module. This is a built-in safeguard to avoid version conflicts, which is a nice win for stability.
If you ever run into duplicate class errors or dependency clashes down the line, you can explicitly force the Fabric version in your build configuration to keep all dependencies aligned.
内容的提问来源于stack exchange,提问作者Ivkin Igor

