android-gradle

Fix duplicate classes and unresolved artifacts by analyzing your dependency graph and version catalogs. Use dependencyInsight to find mismatched variants and duplicate dependencies, then apply minimal version or config changes to resolve the conflicts.

KSP and KAPT integration failures often stem from variant mismatches across multi-module projects. Diagnose these by tying findings to targeted Gradle tasks and verifying AGP, Kotlin, and KSP version compatibility before adjusting your build scripts.

Debug AGP configuration failures by pinpointing problems in your build.gradle, settings.gradle, and libs.versions.toml files. Validate AGP, Kotlin, and KSP compatibility first, then run targeted assemble and dependencies tasks to verify the fixes.

Resolve missing dependencies by preferring dependencyInsight analysis over blind excludes. Inspect your dependency tree to identify mismatched variants or version conflicts, then propose minimal configuration changes with verification steps.

Yes, you can troubleshoot variant and build failures across both debug and release tasks. The process applies evidence-driven reasoning to analyze build scripts and dependency graphs, identifying the root cause of failures in your Android app or multi-module projects.