UI tests blocked by login popup and “bash requesting screen access” dialog in the latest 2025.3 EAP build 253.27864.23

IntelliJ Platform
,
1

I’m running automated UI tests for an IntelliJ plugin on Windows, Linux, and macOS runners (in GitHub) with the latest 2025.3 EAP build 253.27864.23
When the tests start, the following pop-ups appear and block execution:

  • On Windows and Linux, a JetBrains login dialog appears (“Welcome to IntelliJ IDEA EAP – Log in to JetBrains Account”).

    image
    image1182×994 74.2 KB

  • On macOS, in addition to the above, I also get a system popup saying:

    “bash” is requesting to bypass the system private window picker and directly access your screen and audio.

image
image542×678 76.8 KB

Because of these dialogs, the UI tests hang indefinitely since they require user interaction.
Can these login and screen access popups be disabled or skipped somehow when running automated UI tests? Is there an officially recommended setup or configuration for running IntelliJ UI tests in CI environments (Mac, Linux, Windows) so these dialogs don’t appear?

Thanks!

1 Like
3

Hello. Does anybody have any idea regarding this? Any help would be much appreciated. Thanks

6

Hi, @anusreelakshmi2001
Thank you for reaching out to us and for your questions.
Regarding the first one:
Logging in to the JetBrains Account page is expected on all builds without an activated license. Please use this method to add one (and here’s the usage example)

The second issue is way trickier.
Apple Gatekeeper emits the pop-up you see, and you cannot disable or skip it without manual user interaction.
There are two main routes here:
Manually click Allow in this pop-up (or create an AppleScript that will do it in all pop-ups, but you will have to perform user interaction anyway)
Use an older macOS, where the tccutill commands from this page work.

I hope this somewhat helps.

7

Thanks @lev.zagnetin . Just to clarify — do we now need to purchase a license? Earlier, we were using the Community Edition, which didn’t require one. Starting with the 2025.3 release, it seems that the Community Edition is no longer available.

From my understanding, IntelliJ IDEA now offers a free tier beginning with 2025.3, replacing the Community Edition. So, do we need to log in to access the free tier, or is this login requirement only applicable to EAP builds?

This could be an issue for us, as our builds run on GitHub-hosted VMs, where interactive login isn’t possible since there’s no user context or persistent credentials.

8

EAP builds indeed require login or a license

9

Hi

But it wasn’t like this till now – is it something new?

How should we run the ui test in CI with this new policy?

Worth mentioning that in the plugin template you supply a UI testing workflow that will probably break once you upgrade the platform target version.

10

Manually click Allow in this pop-up (or create an AppleScript that will do it in all pop-ups, but you will have to perform user interaction anyway)

@lev.zagnetin I am running my builds in Github VMs. So it’s not possible to have manually click the Allow button. Also I tried interacting with the remote robot and perform click on Allow action. Unfortunately, this is a macOS system security dialog and the Remote Robot is not able to interact with OS-level dialogs.

11

Hi @lev.zagnetin , @yuriy.artamonov… just to clarify, will the upcoming IntelliJ IDEA 2025.3 release (which is the first unified platform release) enforce a login or license? Or will free tier users be able to bypass this?

12

We discuss here only EAP builds

13

I think it won’t help plugin developers to support EAP builds :frowning:
Otherwise, could you update the official plugin template GitHub - JetBrains/intellij-platform-plugin-template: Template repository for creating plugins for IntelliJ Platform ? It would greatly help.

14

I can suggest this solution if you wish to test 2025.3 IDEA EAP without login page:
Use runIdeWithDriver with this vmoption:

.runIdeWithDriver{
  addVMOptionsPatch {
    addSystemProperty("eap.require.license", "release")
  }
}

this will disable Ultimate features in EAP build along with login prompt

cc @anusreelakshmi2001 @jonathanlermitage.1 @tcrawford

1 Like
15

TBH, we also face this issue and currently looking for solution for macOS 15. The only suitable fix for us is using older macOS.

16

What do you mean by disabling ultimate features?

17

Ultimate/paid features in this mode require license just like in release versions. In general you cannot have paid features in real IDE (and in UI tests you have real IDE) without a license or login (in EAP).

It will provide free access although just like unified builds

18

@yuriy.artamonov So, are you saying that the 2025.3 release version will not require a login if we are to use free tier?

19

And if the release will not require- what is the difference?

20

not just the EAP, will also require a login or license?

You seem inattentive to what I write.

  • Paid features require license.
  • Paid features in EAP require login OR license.
  • Free tier does not require license.
  • You may use release flag in EAP, it will turn on free tier there, but not paid features
21

If my understanding is correct, Free tier + EAP will require a login? This is not 100% clear.
And, in this case, we can bypass the login dialog via addSystemProperty("eap.require.license", "release")

You seem inattentive to what I write.

We are attentive, but the discussion is complex…

22

this will disable Ultimate features in EAP build along with login prompt

The release behavior will not require login in EAP builds if you use it. But it will work as a real release requiring a license for paid features.

TL,DR for UI testing you can use

addSystemProperty("eap.require.license", "release")

It will be approximately the same result as the community edition in the past. Free-tier, no login prompt

1 Like
23

Why in Eap it require a login?

Also you wrote both release and eap require license - so what is the difference ?