Introduction

In Gradle, transitive controls whether a dependency pulls in its own dependency tree. With libraries like Crashlytics, this setting affects which supporting artifacts land on your compile and runtime classpaths. Understanding it helps you avoid missing classes, duplicate libraries, and confusing dependency graphs.

What transitive = true Actually Means

A direct dependency may require several internal libraries. When transitive resolution is enabled, Gradle resolves those child modules automatically.

In practice, this means you can declare one top-level artifact and still receive the pieces it needs.

1// build.gradle.kts
2dependencies {
3    implementation("com.google.firebase:firebase-crashlytics") {
4        isTransitive = true
5    }
6}

For most app modules, this is the default and also the expected behavior. Crashlytics depends on other Firebase and Google components, so turning transitive resolution on keeps the integration complete.

What Happens If You Disable Transitive Resolution

If you set isTransitive = false, only the root artifact is included. Child dependencies are excluded unless you add them manually.

1// build.gradle.kts
2dependencies {
3    implementation("com.google.firebase:firebase-crashlytics") {
4        isTransitive = false
5    }
6
7    // If transitive is disabled, required children may need manual declaration.
8    implementation("com.google.firebase:firebase-analytics")
9}

This mode is useful only in controlled cases, such as strict dependency curation or debugging a conflict. For normal app development, it usually creates more work and more risk.

Inspect the Resolved Graph Before and After

Use Gradle reports to see exactly what changed. This is the fastest way to verify whether a missing runtime class is caused by transitive exclusion.

./gradlew :app:dependencies --configuration releaseRuntimeClasspath
./gradlew :app:dependencyInsight --dependency firebase-crashlytics --configuration releaseRuntimeClasspath

When transitive resolution is enabled, you should see Crashlytics plus related modules. With transitive resolution disabled, the tree becomes thinner and often incomplete.

Crashlytics-Specific Integration Advice

For Firebase stacks, use the Firebase Bill of Materials so versions stay aligned across related artifacts.

1// build.gradle.kts
2dependencies {
3    implementation(platform("com.google.firebase:firebase-bom:34.0.0"))
4    implementation("com.google.firebase:firebase-crashlytics")
5    implementation("com.google.firebase:firebase-analytics")
6}

The Bill of Materials reduces version mismatch errors and makes dependency updates safer.

If you intentionally disable transitive resolution for one module, document why and pin all required children explicitly. Otherwise, future updates can silently break the classpath.

Choosing a Strategy for Multi-Module Android Projects

In larger Android repositories, dependency policy should be explicit per module type. Application modules usually keep transitive resolution enabled because they assemble full runtime behavior. Core library modules may disable transitive resolution only when they intentionally expose a narrow API surface and verify required children with tests. Document these rules in build conventions so module owners do not guess. During dependency upgrades, run classpath reports in both debug and release configurations because resolution can differ by variant. A repeatable policy is more valuable than one-off fixes when Gradle graphs become complex.

Common Pitfalls

A common misunderstanding is expecting transitive = true to fix all dependency conflicts. It only controls whether child dependencies are included, not which version wins during conflict resolution.

Another pitfall is disabling transitive resolution to reduce app size without measuring impact. Missing runtime classes and delayed crashes are common outcomes.

Teams also forget that plugins and libraries can inject dependencies through multiple paths. Even if one declaration uses isTransitive = false, another path may still pull the same module.

Finally, avoid mixing manual version pins and platform-managed versions without a clear strategy. Inconsistent version control is a major source of Gradle instability.

Summary

• transitive = true includes child dependencies of the declared artifact.
• transitive = false includes only the root artifact and requires manual child declarations.
• Crashlytics integrations usually rely on transitive resolution to stay complete.
• Use dependency reports to confirm what is actually on the classpath.
• Prefer Firebase Bill of Materials for aligned and maintainable versions.