Hot deploy error after updating plugin to 15.12-262: "Unable to connect to daemon" (Kotlin 1.3.6)

Support
#1

Hello everyone,

After updating the plugin to version 15.12-262, I encountered the following error during hot deploy:

Hot deploy compilation errors: Unable to connect to daemon

Environment details:

  • Kotlin version: 1.3.6
  • Plugin version: 15.12-262

I have tried stopping the Gradle daemons (gradlew --stop) and restarting the IDE, but the issue persists.

Has anyone experienced this daemon connection issue with Kotlin 1.3.6 after the latest plugin update? Any advice on how to resolve it would be greatly appreciated.

Thank you!

#3

Hi Alex,

Here is an IDEA 2026.2 Kotlin plugin compatibility issue that breaks hot-deploy in CUBA plugin.
The problem was fixed and new release 15.13-262 is now available in JetBrains marketplace.

#4

Hi Alexander,

Thank you for the quick update and fix! I installed release 15.13-262, and hot deploy is now working seamlessly again.

Appreciate the support!

Best regards,

Alex

#5

Hi Alexander,

I spoke a bit too soon—there still seems to be an underlying issue.

While the IDE now reports that hot deploy completed successfully without any errors, the actual changes aren’t taking effect. The deployed application continues to run the previous build version instead of updating with the new code.

Could you please look into what might be causing the changes not to apply during the process?

Best regards,

Alex

#6

Hi

Could you please provide any details about the case? What type of file you’ve changed and expect to be hot deployed? So we can reproduce the issue.

#7

Hi Alexander,

Hot deploy works perfectly on the web layer—controllers and their descriptors react to code changes as expected. However, when changing services on the core layer, the IDE reports that the hot deploy was successful, but the actual application state remains unchanged.

Best regards,

Alex

#8

Still can’t reproduce the issue. Service implementation being deployed correctly in my case.

Please attach minimalistic sample project where the issue can be reproduced.

#9

Hi Alexander,

My apologies for the oversight in my previous message!

After double-checking, hot deploy actually works fine for core services as well. The issue specifically occurs with custom @Component classes on the core module—the changes there are not being applied despite the success notification.

Also, I have a minor UX feedback/note: pressing Alt+Enter no longer brings up the “Generate handler” action screen, so I currently have to trigger it manually via mouse click. It’s a bit inconvenient, so if this could be adjusted in a future update, it would be greatly appreciated!

Best regards,

Alex