Compilation failed
When compilation fails, first fix the first explicit source or resource error in the Run window. Treat the failure as an incremental compilation difference only when Gradle succeeds but Jugg still fails.
Q: Java or Kotlin reports a missing symbol
Common messages include unresolved reference and cannot find symbol.
- Run Gradle Sync once.
- If compilation still fails, run a full Gradle build to re-establish the classpath and generated source baseline.
- If Gradle fails, the problem is usually not caused by Jugg.
- If Gradle succeeds but the Jugg failure remains reproducible, report the issue to the maintainers.
Q: Annotation-related or generated source files fail to compile
Jugg supports Compose, @Parcelize, ViewBinding, and DataBinding. For other annotation processors, see Annotation processor support. For annotation processors that are not yet supported:
- Incremental compilation can continue when a change does not affect existing generated code.
- Generated code is not updated when you add or modify an annotation, or change annotation arguments. Run Fallback to Gradle compilation once.
Q: Gradle succeeds, but Jugg still fails
- First run Android Studio Sync once and check whether the problem is resolved.
- If the problem remains reproducible, report the issue to the maintainers.