Closed mbwanajm closed 10 months ago
Thank you for reporting this. I haven't upgraded to 2023.3.1 yet. Will have a look!
This might be related to this plugin verifier issue https://youtrack.jetbrains.com/issue/MP-6157/Plugin-verifier-doesnt-track-transitive-dependencies which incorrectly marks plugin as incompatible.
Where do you see this message? In IntelliJ 2023.3.2 RC I can't see LivePlugin in the plugins marketplace at all :(
You should still be able to install the plugin by downloading it from here https://plugins.jetbrains.com/plugin/7282-liveplugin/edit/versions and use Install Plugin from Disk...
action.
confirming that if you have livePlugin installed in 2023.2.x and upgrade to 2023.3.x the plugin is listed as an installed plugin, but it disables the plugin and marks it as not compatible. when I install a jetbrains ide from scratch, I cant find it in the marketplace at all, probably because it filters incompatible plugins.
you can also see an incompatibility warning in the web page for LivePlugin https://plugins.jetbrains.com/plugin/7282-liveplugin if you have a 2023.3.x ide installed. "Not compatible with the version of your running IDE (PyCharm 2023.3.1, CLion 2023.3.1, DataSpell 2023.3.1) "
I concur with @davecazz, I had LivePlugin installed before upgrading to 2023.3.1, it was disabled immediately after the upgrade restart. I am not quite sure how IntelliJ plugin compatibility works, but from here LivePlugin Marketplace download page version 0.8.6 beta of the plugin is given the compatibility range of 231.7515.13—232.* also shown as the range 2023.1 — 2023.2.5. Just a wild guess here, could these be some manually written metadata in the plugin?
@mbwanajm you're right! I'm not sure how the plugin ended up with an upper version in compatibility range, because I deliberately don't specify it in plugin.xml, e.g. it's just <idea-version since-build="231.7515.13" />
.
I was able though to edit the range for version 0.8.6 on marketplace website so it's now just 231.7515.13+ and should be marked as compatible with the latest IntelliJ versions.
Great this now works.. I have tested it on 2023.3.2