Changes did not take effect
If Jugg reports a successful run but the UI or code still behaves as before, first determine whether the change was not detected, was deployed but requires a restart, or must be updated by a full Gradle build.
Q: How can my Agent investigate changes that did not take effect?
Before restarting or rebuilding, click Ask AI in the Jugg Plugin group of Jugg Running Panel and choose Changes not applied. Describe the changed files and the expected and actual effects, select the affected device, and click Save Evidence and Generate Prompt.
Jugg saves the current logs, logcat for each device, project context, and existing APKs and incremental artifacts, keeping deployed and pending deployment records separate. The evidence manifest records collection failures for the Agent to read using the path in the prompt. A local artifact's existence does not prove that the device loaded it.
Select Copy prompt and paste it into an Agent that can access the current Android project. The prompt requires analysis using the Jugg knowledge base, source code, and saved evidence, with a cause, recommendation, and next step if the problem persists. It provides an Issue draft when needed and identifies specific evidence to collect when information is missing.
Evidence is saved in a separate local directory, survives later builds and Clear Jugg Build, and is retained for 30 days by default. Collect it after the Jugg task finishes. The prompt explicitly permits the Agent to clone Jugg into a separate investigation directory and fetch when necessary; the investigation reads existing evidence only.
The prompt uses Markdown. It is generated in Chinese when the system language is Chinese, and in English otherwise. The Agent uses the same language for its analysis and Issue content. User descriptions and original logs retain their original text; dialog instructions always use English.
When the Agent recommends an Issue, it provides a prefilled bug report link and complete content organized by field. Open the link, review the title, description, and diagnostic information, sign in to GitHub, select the applicable form options, complete the submission confirmation, and submit. If the link is too long or prefilling fails, copy the full content into the corresponding fields. Local evidence files must be provided separately; the link does not attach or upload them automatically.
Q: What should I do when Jugg reports no file changes after I modified a file?
This usually means that the IDE has not yet notified Jugg of the file change, or Jugg's project structure has not been refreshed.
- Cancel the current run and run again.
- If the message still appears, run Gradle Sync once, then run again.
- If the change still does not take effect, run Fallback to Gradle compilation once.
- If the problem persists, report the issue.
Q: Compilation and deployment succeed, but the code still uses the old logic
After you modify startup logic, static declarations, companion object declarations, or Kotlin top-level declarations, the initialization logic for values already initialized in the existing process will not run again if the current deployment uses Hot Reload.
- Use Restart the app to restart the target process.
- If the change still does not take effect after a restart, run Fallback to Gradle compilation once for comparison.
Q: What should I do when style changes do not take effect?
Run Fallback to Gradle compilation once to refresh the result with a full Gradle build.
Generated code was not updated after an annotation change
Jugg runs incremental generation only for annotation processors with a dedicated adapter. An APT, KAPT, or KSP processor outside the supported list does not run automatically during Jugg incremental compilation, so its generated source may remain stale.
- Check Annotation processors to confirm whether the processor is supported.
- If it is not supported, run Fallback to Gradle compilation once to generate the complete result.
- If Gradle works but a supported processor still reproducibly remains stale with Jugg, report the issue.