Diagnosing "plugin was disabled because their counterparts are inconsistent" issue

IntelliJ Platform
,
1

Hi,

While building and testing a plugin in split mode (sandbox IDE or via JB Gateway), I frequently encounter a balloon notification that says

1 plugin was disabled on Frontend and Backend because their counterparts are inconsistent. [plugin name]

I have a few issues/questions regarding this notification:

  • Sometimes it is only the Frontend part that gets disabled, so the message is only partially valid in those cases.
  • In some cases I get this message even with the same exact build but in subsequent IDE launches. Then I do buildPlugin --rerun-tasks once or twice, and the message disappears (ideally).
    • Of course, sometimes it’s obvious that I did misconfigure something.

I tried to look up this notification message, but I didn’t find it in intellij-community or anywhere else, so I couldn’t manage to do any debugging.

I’d like to find out if there is a way to diagnose this kind of issue in detail and get more info on why it happens and what configurations are actually inconsistent.

It was easier to do so when the plugin had only a few modules, but it gets more complex as the number of modules and dependencies grow.

Thanks!