Just to mention a few changes done this past here:
Sorry but I am not sure you guys want to keep the external plugins mechanism at all with all those changes without any public discussion on how it affect us…
Honestly, I’m completely lost.
At least, this is my understanding. I think some clarifications (and put this in the docs) would be helpful, and greater consistency in the advice provided by JetBrains.
We for sure want to help you test with EAP, I am only saying about the compilation with it. This is new change for us on the merge of builds, we simply have not fully adapted to all aspects of it.
The official recommendation is to support 3 Major versions of IDEs and have open until-build to be compatible with the upcoming versions.
Slack is the worst, it was a grave for all knowledge we created. And the huge limitation for the community growth
To me, it feels like the community here has shrunk. Slack was never meant for broad knowledge sharing, but rather for communication within small groups.
Responding to the same people in Slack does not help us anyhow, it is just an elitist club then. And what we needed is searchable and open platform with questions and solutions.
There is no goal to solve exact problems of people who come - this is not support channel, but build a way to help more people with the same problems.
Thank you for the information. You mention that for the 2025.3 release “free tier does not require license”. Does free tier require login? Since this is the first time there will be a “unified build”, we are trying to understand what the behaviour will be so we can properly set up our test automation so it functions when 2025.3 is released.
Logging in is not required in releases for free tier. Please see the official announcement here
You can simply check how PyCharm 2025.2 works and see it as how IntelliJ will do all the same. PyCharm was transformed earlier already
@yuriy.artamonov , thank you for the information, much appreciated.
Thank you @yuriy.artamonov
Hi @lev.zagnetin . Were you able to figure out a solution on how to use macOS 15 to run automation ?
Hi, @anusreelakshmi2001, unfortunately, no, it very much depends on how you build images. We’re currently investigating if we can use java.awt.robot to click and accept all System Settings prompts, but I can’t share results. Moreover, I can’t promise that our solution is usable with GitHub’s agents, since our infra is very different and allows using tccutill.
If you happen to discover something that can help, we would be happy to hear your findings.
Hi, @anusreelakshmi2001
After some research, we’ve finally found a fix for the window picker popup by updating ~/Library/Group Containers/group.com.apple.replayd/ScreenCaptureApprovals.plist. Here’s a GitHub link with a sample script that does it. Let us know if it helps, and have a happy holiday!