Unit test failure seems unrelated to this change 🤔

Also the fail in the appveyor CI seems unrelated as it is some error in the redis integration test for the messenger component 🤔

friendly ping@HeahDude as you contributed this feature, thanks

I could not reproduce the issue#52433.

This listener is part of theFrameworkBundle, and so it should be used withSymfony\Bundle\FrameworkBundle\Console \Application. Could you provide more details on your application or test setup?

Ok took a look again and seemed i messed something up with the command tester, that seems to work as it does not dispatch the event.

However manually triggering events by dispatching theConsoleCommandEvent does not work anymore.
E.g.

$commandEvent =newConsoleCommandEvent($command,$input,$output);$kernel->getContainer()->get('event_dispatcher')->dispatch($commandEvent, ConsoleEvents::COMMAND);

We used something like that in an internal command tester, that's why i first assumed the issue is in the symfony command tester as well.

However, I still think the fix makes sense, as you should not rely in the listener that the event was correctly configured in the application class. IMHO the benefit of using events is to decouple different parts of the system from each other, but this assumption (that there is always anprofile option) in the listener basically couples the listener to the application class-

I've no strong opinion here. I think I can live with that coupling, especially given it's part of a bundle

Thank you@keulinho.