In then error report dialog, would it be possible to just report to the Marketplace by default instead of not reporting at all?
I‘ve seen many plugin which don‘t have any error reporter at all and thus never see the exceptions the plugins are causing. If a plugin implements its own error reporter extension, then that would be used instead, just like before.
Since 2026.3 release if you use JetBrainsMarketplaceErrorReportSubmitter you get all exceptions from all users reporting errors/freezes automatically. No dialog is shown in that case.
This will become especially powerful once we enable automatic reporting for 100% users by default, at the moment it is enabled for around 7% of our total user base.
We may include JetBrainsMarketplaceErrorReportSubmitter to new plugin template probably.
The docs have been updated quite recently, even on the JetBrainsMarketplaceErrorReportSubmitter.
Will the automatic error reporting only be enabled for the JetBrainsMarketplaceErrorReportSubmitter or also for 3rd-party implementations?
For various reasons, I prefer my own implementation and endpoint.
Yes, only for data sent to us, unfortunately we may not send data to 3rd party silently. In case of JetBrainsMarketplaceErrorReportSubmitter it is our Privacy Policy that covers it
Understandable.
But in that case why not send to the marketplace by default as a fallback if no error reporter is configured? That would (probably) be a great improvement for every plugin on the Marketplace which has not yet its own — the exceptions tab is always visible now for every plugin.
Just a thought, I have my own error reporting, anyway.
It’s all unclear and depends heavily on plugin developers’ expectations. Basically, if they don’t care and don’t visit the Marketplace, those will just be ignored and go to /dev/null. If no reporter is configured, errors are shown to users, who can see which plugin they’re attributed to — this way, at least users can report them to the authors.
Can I offer a counter argument about exception reporting?
A developer may be working on a project that are confidential, proprietary, or otherwise sensitive.
Submitting an exception may contain information about their project, their machine or other info. It could also contain their code.
I would include paths in this as well.
I may feel okay, with my consent, sending this to JetBrains.
Automatically, to plugin developers? No.
I want users to submit exceptions to us, badly, via the JB Exceptions, but I want them to understand what they are submitting, which I’ve been happy with - read what we get in the window that shows, click Report Exception.
Doing this automatically by default to plugin developers feels weird, but I would love for this to be a checkbox of “Send this plugin exceptions automatically” or something.
It’s why the settings page clearly states this (it’s good) to the user.
Sending this to plugin developers, by default. feels weird/uncomfortable, personally.
Submitting an exception may contain information about their project, their machine or other info. It could also contain their code.
We do error message sanitization in auto-submitted errors and no attachments are allowed in such cases, it is heavily regulated area and we may only do that if we clear all suspicious things from messages.
Also, IDE knows exactly which plugin IDs are originated from Marketplace, so no any communication with it about any plugins not published there
