-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
The path you passed as the first argument does not exist. Check the path to the project or module. Remember you can use . if you're already inside the directory.
The dynamic engine (--engine dynamic or auto) could not configure the build. Common causes:
- No JDK available or not on
PATH. - No Gradle wrapper (
gradlew/gradlew.bat) at the project root. - The project build fails during configuration.
Solution: use the static engine (--engine static, the default) — it requires no JDK or wrapper and only reads text. See Static vs Dynamic Engine.
- For
.ktsfiles, install the AST parser:pip install tree-sitter tree-sitter-kotlin(orpipx install "android-gradle-analyzer[kts]"). Without it,.ktsfiles are parsed with regex and multiline or commented-out cases may be missed. - For
.gradlefiles, the preprocessor already handles multiline and comments. If the problem persists, check the recognized scopes inanalyzer_utils.py(constantDEPENDENCY_SCOPES). - For full accuracy with Version Catalogs, variables, or convention plugins, use
--engine dynamicon a trusted repo.
Install the package in editable mode: pip install -e . (or pip install -e ".[kts,yaml]" for all optional features).
Increase the spacing values in gradle_analyzer.py (generate_plantuml()). See the spacing table in How it works. For large projects, you can also scope the graph with gradle-analyzer <path> --focus <module> or analyze submodules separately.
- Requires
pyyaml:pip install "android-gradle-analyzer[yaml]". If not installed, the yml is silently ignored without error. - The yml is looked up from the path you pass as the first argument, not from the CWD.
- Remember that CLI flags always override the yml. See Configuration.