License Check with IDEA 2019.2 beta returns null - no license, no popup to evaluate plugin
Hi,
I currently test my paid plugin with IDEA EAP 2019.2 beta. If I start the plugin within the IDE plugin development I got no longer the popup for evaluation of the plugin and later, the license check always returns false.
This is du to return null from
final String cstamp = facade.getConfirmationStamp(PRODUCT_CODE);
if (cstamp == null) {
return false;
}
(from https://plugins.jetbrains.com/docs/marketplace/add-marketplace-license-verification-calls-to-the-plugin-code.html -> isLicensd)
There are messages in the idea log file about repository issues
2019-07-04 16:55:58,592 [ 442341] INFO - .ide.plugins.PluginManagerMain - https://www.jetbrains.com/intellij-repository/releases/
java.io.IOException: org.xml.sax.SAXParseException; lineNumber: 6; columnNumber: 6; The element type "meta" must be terminated by the matching end-tag "</meta>".
at com.intellij.ide.plugins.RepositoryHelper.parsePluginList(RepositoryHelper.java:221)
at com.intellij.ide.plugins.RepositoryHelper.lambda$loadPlugins$1(RepositoryHelper.java:153)
Should paid plugins / license check work with EAP 2019.2 beta / EAP Repositories?
Please sign in to leave a comment.
Hi Thomas,
There are no licenses in IDEA EAP because it's EAP, maybe it will be added there in the future. So the license check always shows false and license window doesn't appear. We recommend setting "until build" (http://www.jetbrains.org/intellij/sdk/docs/basics/plugin_structure/plugin_configuration_file.html) for paid plugins to release version (191.* or 192.0 for now) to users of the plugin don't get into the situation when they bought the plugin but cannot use it, because they have only EAP (until the license checking is added there) .
There is the same situation in all community products (such as IntelliJ IDEA Community, Android Studio, etc.). So we advise adding com.intellij.modules.ultimate dependency to plugin.xml file (http://www.jetbrains.org/intellij/sdk/docs/basics/getting_started/plugin_compatibility.html) to restrict compatibility of your paid plugin only with the paid products.
When licenses are available in Community Products and EAP we will notify about it all developers of paid plugins.
Another option would be to always allow your plugin to run within an EAP release. For instance:
For the time being I also enable my paid plugin in Community releases via limiting my license check to Ultimate releases:
Hi, Lidiya, Scott,
thanks for clarification and the idea. No I can decide how to proceed further.