Package com.intellij.platform.rpc is marked internal in 2025.3

IntelliJ Platform
1

Hi all,

I started converting my plugin on remote, but I found the first “issue”, the package com.intellij.platform.rpc is marked as internal:

//
// Source code recreated from a .class file by IntelliJ IDEA
// (powered by Fernflower decompiler)
//

@Internal
package com.intellij.platform.rpc;

import org.jetbrains.annotations.ApiStatus.Internal;

This in package-info.java

Can I ignore it?

Regards,
Mirko

2

In addition I don’t understand why the pacakge com.intellij.util.ui is in the VCS Implementation module, I suppose should be more in the frontend one

3

Could you please share some examples where do you face with a problem

4

My question is more: can I ignore the Internal Api warning in this scenario and will not block the publishing?
About the other question I just remove the dependency on that package in my code.

5

Sorry, but I don’t understand where do you face it first of all

6

Oh, I see there is no highlighting for that in IDE but the package is indeed marked Internal. Such a pity!

We are going to quickly iterate on it and make it public in 2025.3.4 builds soon! This will effectively unblock its usage in previous versions as well.

7

With 2026.1 rc the package is not internal anymore.

But plugin verifier still complains, apparently about code generated by the RPC gradle/kotlin compiler plugin.

What’s the recommendation for this?

image
image2719×763 245 KB

9

Does the Plugin Verifier complain on local runs as well?

10

The screenshot above was from a local run. I have not yet published the changes on the Marketplace. I’m not sure what the online verifier would report.

11

we’ll anyways fix that as well, thanks a lot for pointing to the problem

12

Thank you!

Which release is planned to have the fix?
I hope I’ll be able to publish a plugin even with these violations, as there’s nothing I could do about it.

14

will do asap, I suppose the next minor update 2025.3.4 will have the update inclued. It does not have a release date yet. Should you have troubles uploading the plugin before this release, please ping us, we will assist. It’s clearly a bug on our side

15

May i ask you to verify if you see internal api violations with ij gradle plugin 2.13.1 and idea 2026.1 as target ide?

I went to fix the problem and at least with 26.1 release it seems to be no longer there..

16

Yes, I’m still seeing the internal api usages with 2026.1.

The RPC Gradle plugin and the kotlinx-serialization Gradle plugin are applied in the setup.
Building against “IU-2026.1”.

Relevant snippet of the RPC Service interface:

@Rpc
interface NoctuleStatusService : RemoteApi<Unit> {
    companion object {
        suspend fun getInstanceAsync(): NoctuleStatusService {
            return RemoteApiProviderService.resolve(remoteApiDescriptor<NoctuleStatusService>())
        }
    }

// removed some methods

    @Suppress("UnstableApiUsage")
    suspend fun getStatusUpdates(projectId: ProjectId): Flow<StatusEvent>
}

Screenshot:

image
image1920×1029 355 KB

17

Hey, I’ve updated the api statuses, and now marketplace must accept their usages. Note this applies for a verification performed during the plugin upload.

Local verifier runs currently will still produce errors that are no longer relevant. Please, ignore them