SonarQube for IntelliJ plugin version: 10.23.0.81344
IntelliJ version: 2025.1.1.1 (Build #IU-251.25410.129, built on May 9, 2025)
Programming language you’re coding in: Java, TS
Is connected mode used:
SonarQube Community Build? (if one of the latter two, which version?): Community Edition v10.7 (96327)
And a thorough description of the problem / question:
I can see the following exception in IntelliJs logs:
WARN - #c.i.i.s.i.StartupManagerImpl - Migrate org.sonarlint.intellij.StartServicesOnProjectOpened to ProjectActivity [Plugin: org.sonarlint.idea]
com.intellij.diagnostic.PluginException: Migrate org.sonarlint.intellij.StartServicesOnProjectOpened to ProjectActivity [Plugin: org.sonarlint.idea]
at com.intellij.ide.startup.impl.StartupManagerImpl.doRunPostStartupActivities(StartupManagerImpl.kt:293)
at com.intellij.ide.startup.impl.StartupManagerImpl.access$doRunPostStartupActivities(StartupManagerImpl.kt:70)
at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$3$2.invokeSuspend(StartupManagerImpl.kt:193)
at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$3$2.invoke(StartupManagerImpl.kt)
at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$3$2.invoke(StartupManagerImpl.kt)
at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:62)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:163)
at kotlinx.coroutines.BuildersKt.withContext(Unknown Source)
at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$3.invokeSuspend(StartupManagerImpl.kt:192)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:608)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:873)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:763)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:750)
Is the current version of the plugin not compatible with the latest version of IntelliJ?
Thanks for the information. Unfortunately the plugin does not work anymore. It starts scanning in the background (I can see the progress bar) but it never finishes. So I was checking the logs. And this is the only exception I could find.
Is there a possibility to debug the issue further on my side?
We are using sonarqube from the company we are working for as a supplier. So I don’t have much influence on the server side. Hence I need more information from client side before creating an issue on their side.
Hello Nicolas!
Thanks for your help. Our SonarQube server has been updated to the latest version and since that the plugin is working fine again. So was definitely a problem on the server side or on the connection. Can’t tell. So this issue can be closed.
KR, Chris
If you’re getting exceptions with the SonarQube plugin in IntelliJ IDEA 2025.1.1.1, it could be due to a version mismatch between the plugin and the new IDE build. Major IntelliJ updates often introduce breaking changes that third-party plugins like SonarLint or SonarQube for IDE might not yet support.
Here are a few troubleshooting tips:
Check compatibility – Make sure you’re using the latest version of the SonarQube plugin (or SonarLint) that explicitly supports IntelliJ 2025.1.1.1. Older plugin versions may not be compatible with the latest API changes.
Review stack trace – Look at the specific exception message in IntelliJ’s logs (Help > Show Log in Explorer/Finder). It may point to missing classes or deprecated method calls.
Plugin conflict – Disable other code analysis or quality plugins temporarily to check for conflicts.
Roll back IntelliJ (if critical) – If the plugin is essential and no patch is available, consider rolling back to IntelliJ 2024.x where plugin stability is confirmed.
Temporary workaround: Use SonarLint standalone with manual configuration or rely on command-line SonarQube analysis until the plugin update is released.