The issue IMO is the order of compiler passes: registering listeners should be done before resolving service decoration, so that the decorated service is registered as a listener with its original id (and so the decorator service will then be used when calling the listener) instead of registering it with its internal generated id (which would not call the decorator service, even if we keep it public to allow lazy-loading).

@symfony/deciders I suggest that the resolution of service decoration is kept as late as possible, so that all compiler passes collecting services based on their tags are applied before that, so that they collect the original id (and so take service decoration into account). This would mean making it run at the very end of the "before optimization" passes, even after passes added by other bundles (which can be achieved in 3.2 as we added a concept of priorities). What do you think about that ?

Sounds like a reasonable solution. This will also solve the use cases where you had to duplicate tag definitions from the decorated service.

@xabbuh Does #20207 change anything about this issue?

@teohhanhui Any version including the fix from #20207 shouldn't suffer from the limitation you pointed out anymore. However, we may want to think about whether there are still other advantages of changing the order in which the compiler passes are executed.

Shall we close this one?