Custom Macro fails to resolve Project in Run Configurations (regression in 2026.1)

IntelliJ Platform
1

Hello,

I’ve encountered a regression in the IntelliJ Platform SDK version 2026.1 (Build 261). My custom Macro implementation can no longer retrieve the Project instance from the DataContext when the macro is expanded during a Run Configuration execution.

In previous versions (2024.x, 2025.x), the following code worked correctly:

override fun expand(dataContext: DataContext): String? {
    val project: Project? = CommonDataKeys.PROJECT.getData(dataContext)
    // project is null here in 2026.1
    val configService = project?.service<ConfigService>()
    val database = configService?.selectedDatabase
    if (!database.isNullOrEmpty()) {
        return database
    }
    return ""
}

Is this a known change in the DataContext lifecycle for 2026.1, or should I be using a different key to access the project context during macro expansion?

It appears this is not limited to custom macros. Standard built-in macros like $FileName$ or $ProjectFileDir$ also fail to expand correctly or return empty values when used in the same context (Run Configuration arguments) in Build 261. This suggests a broader issue with MacroManager or DataContext propagation during the execution phase in the latest 2026.1.

Thanks for any help!

2

Seriously, what’s the point of this website? I reported a serious issue and received no response or feedback.

3

This website is a community effort, and people may be on vacation :wink:
Be patient and don’t be insulting, otherwise you should expect nothing from us.

4

We also would be glad to receive issues where they belong - issue tracker https://youtrack.jetbrains.com/issues/IJPL

This is how problems become visible to the development team

5

I did report this issue via the issue report, but I haven’t received any response yet.

6

Hi, @tadeuszkarpinski, please provide the YouTrack issue number for further investigation.

7

For the past 24 days, I’ve been getting emails from users asking why my plugin no longer works. The user base I spent a long time building is now essentially gone - and more importantly, the trust is gone too. That’s not something you just recover later.

This was supposed to be fixed within two weeks - it’s now been four. The pre-release build has been in testing for over a week with no visible progress or clear communication.

At this point, I’ve lost confidence in how this is being handled. Can you explain what’s actually happening and when this will realistically be resolved?

8

Hello again,

it would really help to provide the YouTrack issue number to investigate and escalate, if necessary. Thank you!

9

Since your team seems too busy ‘shaping the future’ to look at your own bug tracker, here is the link: https://youtrack.jetbrains.com/issue/PY-88858

I know it’s hard to find anything in that pile of 2.2 million issues, so I did the job for you. You’re welcome. Now, maybe stop the ‘vibe coding’ and actually fix it?

10

To repeat the YouTrack status:

You can already use the 2026.1.1 RC available via the Toolbox App or direct download.

11

Since you’re suggesting using the pre-release build, could you add some kind of notification when users are about to uninstall my plugin?

Something suggesting they switch to the 2026.1.1 RC.

Right now, users just uninstall the plugin when it stops working - and they don’t come back.

12

Moreover, 2026.1.1 release is available today

13

Interesting how the release suddenly went from “in the next few days” to “available today.”

14

For us the release is a week when we release all products, they rarely appear on a single date

15

I don’t care, should I?

16

It took 23 days for you to mention YouTrack issue here

Such attitude does not help your users.

17

Which users? They are all gone now. Thanks to you