We have currently solved it with this in our Kernel.php (thx @Ilyes512 ) but we are not sure if we experince problems in the future. The reference.php interferes the freshness check in shared kernel app

    #[Override]
    protected function getKernelParameters(): array
    {
        $parameters = $this->getKernelParametersTrait();

        $parameters['kernel.application_id'] = $this->getApplicationId()->value;
        $parameters['kernel.tenant_id'] = $this->getTenantId()->value;

        // Should only be used by PhpConfigReferenceDumpPass to generate the config reference for the app config dir
        // parameter.
        $parameters['.kernel.config_dir'] = $this->getBuildDir();

        return $parameters;
    }
    ```

This file only depends on the bundles that are enabled in your dev environment.

Yes, which are different ones per apps, so the file constantly changes after swithcing apps, causing cache invalidation issues (in dev mode)

The above snippet is not really a fix it's more of a workaround since the files now land in de build dir wish is inside the var dir assuming default config. Both my editor and the static code tool won't parse the file.

Being able to just turn this feature off would be even better.

This file only depends on the bundles that are enabled in your dev environment.

We are using a Shared Kernel setup where depending on an env var the loaded config, bundles etc are different. And so yes, that would mean a different reference file depending on the current shared kernel being loaded.

With reference.php per app, we will have copied definitions for shared bundles in each reference.php file. IMO we should have the ability to configure shared reference.php for shared bundles and app-specific reference.php for app-specific bundles. However, at the moment of creation reference.php, we don't know which bundles are shared and which are app-specific, because in the shared kernel config, all bundles are merged into one flat array.

Totally agreed. When I use YAML config, I don't even need this file. Separate console command would be the most flexible idea.

Do you know if there is an open issue for this? This is happening to us quite frequently, too. I can imagine the bigger the team this gets quite annoying.