I uploaded my plugin to the plugin marketplace, and it prompted that there are 7 critical issues (marked in red) that need to be fixed. I used intelliJ-plugin-verifier (version 1.388) to scan my plugin package, and the scan results showed dozens of issues, none of which were marked as critical (in red). How can I determine which issues in my own scan results will be intercepted by the plugin marketplace?
As shown in the figure, the left side is the result of the plugin marketplace scan, and the right side is the result of my own scan.
May I ask, the plugin marketplace has also detected some compatibility problems. After analysis, some of them are false positives. How should we handle these?
In addition, for the issues identified by the plugin marketplace, we have analyzed them and provided email responses. However, we have not yet received any response from the plugin marketplace. Could you please help inquire about this?
CefBrowser.getTools() has a dedicated discussion: Accessing DevTools Programmatically in IDEA 2025.3 . Note that the Plugin Verifier is not able to distinguish between production usage and internal debugging usage. All code inside the plugin artifact is considered to be production ready.
The same holds for CefRequestHandlerAdapter that is a part of 3rd party library that triggered an incompatible API change.
ContentImpl.get()method is simply not available. If you target multiple major API changes, the recommended strategy is to build multiple versions of plugins, compatible with specific target IDEs. Reflection is discouraged, but this usage is not even reflection-based. Furthermore, reconsider this particular API usage, as the Impl suggests that this API is more like internal.
Missing com.huawei.deveco: did you declare this dependency as optional in the plugin descriptor?
We at JetBrains are reading multiple channels. It is ok to sent an email, but for purely technical questions, this JetBrains Platform forum is the best place to discuss. We can escalate to proper teams or even answer directly.