Troubleshooting
March 25, 2026 ยท View on GitHub
How To Use This Page
- Match your symptom.
- Run listed quick checks.
- Apply fix.
- Re-run
:checkhealth androidif environment-related.
Health Check Baseline
Run :checkhealth android from project root.
Checks cover SDK discovery, sdkmanager, avdmanager, adb, emulator, aapt2,
Gradle command resolution, and iOS tooling on macOS.
Common Symptoms
SDK Not Found
Quick checks:
- Ensure
ANDROID_SDK_ROOTorANDROID_HOMEis set. - Confirm
local.propertieshassdk.dir=/path/to/sdkwhen used.
Fix:
- Set
sdk.rootin setup if auto-discovery is not stable in your environment.
Gradle Not Found
Quick checks:
- Ensure
./gradlewexists at workspace root.
Fix:
- Set
build.gradle_commandto a valid command or path.
No Android Targets Detected
Quick checks:
- Ensure
com.android.applicationorcom.android.libraryplugin is applied. - For version catalogs, verify plugin alias is one of supported Android forms.
- In composite builds, verify the root
settings.gradle[.kts]includes the expectedincludeBuild(...)entries and each included build has its ownsettings.gradle[.kts].
Fix:
- Ensure
namespaceexists when relying on namespace detection. - If build-file scans look stale, reopen AndroidMenu or rerun an explicit Gradle action so task/snapshot-based discovery can refresh module detection.
Telescope Missing
Quick checks:
- Confirm Telescope is installed if you expect Telescope UI.
Fix:
- Plugin will use
vim.uifallback automatically.
Run Configs Not Loading
Quick checks:
- Confirm
run.config_pathpoints to valid JSON. - Confirm path is absolute or workspace-relative as intended.
- If you use
.android.nvim.json, validate the whole file: the same JSON may be read for run configs,app.package, andbuild.apk_overrides.
Fix:
- Correct malformed JSON. The plugin warns once per broken file path with
Invalid shared project config JSON in ... Check JSON syntax.
APK Not Found
Quick checks:
- Confirm selected variant was built.
- Confirm any
build.apk_overridesentry matches both module and variant.
Fix:
- Enable
build.scan_all_apk_outputs = truefor recursive output scan fallback.
Gradle Prefetch Warning
Quick checks:
- Read the warning text; it includes the first useful Gradle failure line.
- Confirm
build.gradle_commandresolves correctly for this workspace. - Re-run the failing Gradle command manually if you need full output.
Fix:
- Fix the Gradle/workspace issue, then reopen AndroidMenu or rerun
:AndroidGradleTasks/:AndroidBuildPromptto refresh prefetch data.
Related Docs
- Getting started: ../getting-started.md
- Run config guide: ../guides/run-configs.md