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: 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.