#108349TYPO3 Exceptions after update “symfony/dependency-injection” to "7.4.0"
Description
I recently did an update of all the packages in TYPO3 v13 and now I’m getting errors when running the CLI command vendor/bin/typo3 cache:flush or other ones. Also the frontend starts showing errors. It seems to be related to the package “symfony/dependency-injection”, version “7.4.0”.
The error I first get is
Uncaught TYPO3 Exception Interface “TYPO3\CMS\Reports\StatusProviderInterface” not found
thrown in file /path_to_website/vendor/typo3/cms-install/Classes/Report/EnvironmentStatusReport.php
in line 34
This is true because we do not have the TYPO3 core reports package installed. But that was never a problem. Now it suddenly seems to be an DI issue.
My installation was running on “symfony/dependency-injection” version “7.3.6” half an hour ago and then it worked fine. I now have this package fixed to version “7.3.6” and everything is working fine again. The release of the newer version was today (2025-11-27) at 13:27 UTC
Reviews 6
- 12.4 91943[BUGFIX] Account for symfony/dependency-injection:7.4 incompatibility
- 13.4 91941[BUGFIX] Account for symfony/dependency-injection:7.4 incompatibility
- main 91926[BUGFIX] Account for symfony/dependency-injection:7.4 incompatibility
- 12.4 91923[BUGFIX] Mitigate "TYPO3\CMS\Reports\StatusProviderInterface" not found
- 13.4 91922[BUGFIX] Mitigate "TYPO3\CMS\Reports\StatusProviderInterface" not found
- main 91921[BUGFIX] Mitigate "TYPO3\CMS\Reports\StatusProviderInterface" not found
Related issues 1
Files 1
History 1629
Show 4 earlier messages
-
Lars Peter Søndergaard commented and changed attached TYPO3 Exception.html <span data-processor="relativetime" data-value="2025-11-27T14:53:09+00:00" > 11/27/25, 14:53 </span>
-
Patrick Broens changed subject
Uncaught TYPO3 Exception Interface "TYPO3\CMS\Reports\StatusProviderInterface" not foundTYPO3 Exceptions after update “symfony/dependency-injection” to "7.4.0" <span data-processor="relativetime" data-value="2025-11-27T14:54:14+00:00" > 11/27/25, 14:54 </span> -
Lars Peter Søndergaard changed
TYPO3 Exception.html<span data-processor="relativetime" data-value="2025-11-27T14:55:47+00:00" > 11/27/25, 14:55 </span> -
Tomas Norre Mikkelsen commented <span data-processor="relativetime" data-value="2025-11-27T14:56:21+00:00" > 11/27/25, 14:56 </span>
I have the same error.
From what I see, there is a missing dependency.
`typo3/cms-install/Classes/Report/EnvironmentStatusReport.php` implements `StatusProviderInterface` from `typo3/cms-reports` but there is no dependency for that in composer.json
If I install `typo3/cms-reports` manually. I run into the next dependency error, so looks like some dependencies which are followed through.
`Interface “TYPO3\CMS\Dashboard\Widgets\WidgetInterface” not found`
-
Lars Peter Søndergaard commented and changed attached TYPO3 Exception.html <span data-processor="relativetime" data-value="2025-11-27T14:58:13+00:00" > 11/27/25, 14:58 </span>
(had to deleted it once)
-
Patrick Broens commented <span data-processor="relativetime" data-value="2025-11-27T15:07:21+00:00" > 11/27/25, 15:07 </span>
This also happens in TYPO3 v12, not only v13
-
Randy Fay commented <span data-processor="relativetime" data-value="2025-11-27T15:48:44+00:00" > 11/27/25, 15:48 </span>
DDEV automated test failure resulting from this: https://github.com/ddev/ddev/pull/7909
-
Nikita Hovratov commented <span data-processor="relativetime" data-value="2025-11-27T16:11:37+00:00" > 11/27/25, 16:11 </span>
This is the “bad” patch form symfony that causes this problem: https://github.com/symfony/dependency-injection/commit/e58da973e98fd3460813a02203d9987fa664863c
Means: All Classes which are loaded with DI and implement a non-existing interface are affected, eventhough they are otherwise unused in the code base.
This affects extensions like b13/container or mask, which support multiple TYPO3 versions in one version.
For reference: This was reported for Mask some days ago already: https://github.com/Gernott/mask/issues/685#issuecomment-3557891038
-
Gerrit Code Review pushed patch set 1 for main to change 91921 status
NewUnder Review <span data-processor="relativetime" data-value="2025-11-27T21:27:18+00:00" > 11/27/25, 21:27 </span> -
Gerrit Code Review pushed patch set 2 for main to change 91921 <span data-processor="relativetime" data-value="2025-11-27T21:29:07+00:00" > 11/27/25, 21:29 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 91921 <span data-processor="relativetime" data-value="2025-11-27T21:44:07+00:00" > 11/27/25, 21:44 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 91922 <span data-processor="relativetime" data-value="2025-11-27T21:44:48+00:00" > 11/27/25, 21:44 </span>
-
Gerrit Code Review pushed patch set 1 for 12.4 to change 91923 <span data-processor="relativetime" data-value="2025-11-27T21:51:50+00:00" > 11/27/25, 21:51 </span>
-
Gerrit Code Review pushed patch set 2 for 12.4 to change 91923 <span data-processor="relativetime" data-value="2025-11-27T22:15:13+00:00" > 11/27/25, 22:15 </span>
-
Tomas Norre Mikkelsen commented <span data-processor="relativetime" data-value="2025-11-28T07:07:54+00:00" > 11/28/25, 07:07 </span>
I also have a similar error in my tests after installing `“symfony/dependency-injection:7.4.0”`,
I haven’t had time to test the Patch Set, but wanted to inform if related. My tests works again as soon as I downgrade `symfony/dependency-injection` to `7.3.6`.
This only fails for TYPO3 14.0 though. The TYPO3 13 LTS still works for my tests even with `“symfony/dependency-injection:7.4.0”` installed.
1) AOE\Crawler\Tests\Functional\Hooks\ProcessCleanUpHookTest::crawlerInitCallsBothCleaners Symfony\Component\DependencyInjection\Exception\InvalidArgumentException: Cannot generate lazy proxy for service ".lazy.TYPO3\CMS\Core\Site\Set\SetCollector". /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/symfony/dependency-injection/LazyProxy/PhpDumper/LazyServiceDumper.php:181 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/symfony/dependency-injection/Dumper/PhpDumper.php:589 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/symfony/dependency-injection/Dumper/PhpDumper.php:230 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/cms-core/Classes/DependencyInjection/ContainerBuilder.php:154 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/cms-core/Classes/DependencyInjection/ContainerBuilder.php:85 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/cms-core/Classes/Core/Bootstrap.php:130 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/testing-framework/Classes/Core/Testbase.php:754 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/testing-framework/Classes/Core/Functional/FunctionalTestCase.php:429 /home/tomas/Projects/TYPO3/ext-crawler/Tests/Functional/Hooks/ProcessCleanUpHookTest.php:49 /home/tomas/Projects/TYPO3/ext-crawler/.Build/bin/phpunit:122 Caused by Symfony\Component\VarExporter\Exception\LogicException: Cannot generate lazy proxy: leverage native lazy objects instead for class "TYPO3\CMS\Core\Site\Set\SetCollector". /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/symfony/var-exporter/ProxyHelper.php:47 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/symfony/dependency-injection/LazyProxy/PhpDumper/LazyServiceDumper.php:179 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/symfony/dependency-injection/Dumper/PhpDumper.php:589 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/symfony/dependency-injection/Dumper/PhpDumper.php:230 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/cms-core/Classes/DependencyInjection/ContainerBuilder.php:154 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/cms-core/Classes/DependencyInjection/ContainerBuilder.php:85 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/cms-core/Classes/Core/Bootstrap.php:130 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/testing-framework/Classes/Core/Testbase.php:754 /home/tomas/Projects/TYPO3/ext-crawler/.Build/vendor/typo3/testing-framework/Classes/Core/Functional/FunctionalTestCase.php:429 /home/tomas/Projects/TYPO3/ext-crawler/Tests/Functional/Hooks/ProcessCleanUpHookTest.php:49 /home/tomas/Projects/TYPO3/ext-crawler/.Build/bin/phpunit:122
-
Manfred Egger commented <span data-processor="relativetime" data-value="2025-11-28T07:30:22+00:00" > 11/28/25, 07:30 </span>
We have a similar problem. The patchset does not solve this for us, because the current state of the patchset only changes- EXT:install
- EXT:redirects
- EXT:extensionmanager
But in our case we have EXT:seo installed but not EXT:dashboard. So this error occurs:
@Uncaught TYPO3 Exception Interface “TYPO3\CMS\Dashboard\Widgets\WidgetInterface” not found@So I think the patchset needs to be adapted so that all core extensions with optional/suggested dependencies which possibly are not installed are needed to be changed in a similar manner. imho this also applies to every “external” extension with optional dependencies.
As this cannot be handled in some of our installations, we stick to version 7.3.6 of symfony/dependency-injection atm.
-
Gerrit Code Review pushed patch set 1 for main to change 91926 <span data-processor="relativetime" data-value="2025-11-28T08:05:24+00:00" > 11/28/25, 08:05 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 91926 <span data-processor="relativetime" data-value="2025-11-28T08:08:18+00:00" > 11/28/25, 08:08 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 91926 <span data-processor="relativetime" data-value="2025-11-28T08:41:18+00:00" > 11/28/25, 08:41 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 91926 <span data-processor="relativetime" data-value="2025-11-28T08:47:42+00:00" > 11/28/25, 08:47 </span>
-
Xavier Perseguers commented <span data-processor="relativetime" data-value="2025-11-28T09:41:04+00:00" > 11/28/25, 09:41 </span>
Just had the same problem in TYPO3 v12, this time related to sysext “seo” (cms-seo). Interface WidgetInterface used by PagesWithoutDescriptionWidget. I’m not using that widget and cache:flush fails.
-
Gerrit Code Review pushed patch set 5 for main to change 91926 <span data-processor="relativetime" data-value="2025-11-28T09:56:18+00:00" > 11/28/25, 09:56 </span>
-
Benjamin Franzke changed category target version <span data-processor="relativetime" data-value="2025-11-28T09:57:59+00:00" > 11/28/25, 09:57 </span>
-
Christian Huppert commented <span data-processor="relativetime" data-value="2025-11-28T12:22:42+00:00" > 11/28/25, 12:22 </span>
Can also confirm Lars Peter Søndergaard’s description:
It also happens with the Extension b13/container, as it's referencing NewContentElementWizardHookInterface that no longer exists (for compatibility with older versions in a Hook). So it can't really be fixed by only installing typo3/cms-report. A downgrade of that symfony dependency was necessary. Greetings lps
Downgrading to symfony/dependency-injection:7.3.6 – the latest release before 7.4.0 – resolved the issue.
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 91941 <span data-processor="relativetime" data-value="2025-12-01T09:12:15+00:00" > 12/01/25, 09:12 </span>
-
Gerrit Code Review pushed patch set 1 for 12.4 to change 91943 <span data-processor="relativetime" data-value="2025-12-01T09:58:48+00:00" > 12/01/25, 09:58 </span>
-
Benjamin Franzke commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-12-01T10:40:10+00:00" > 12/01/25, 10:40 </span>Applied in changeset commit:09435442521a889a9e6d8ca10c67f5481057d5d2.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T11:48:37+00:00" > 12/02/25, 11:48 </span> -
Stefan Froemken changed Related to #109441 <span data-processor="relativetime" data-value="2026-03-31T13:28:49+00:00" > 03/31/26, 13:28 </span>
Can confirm.
It also happens with the Extension b13/container, as it’s referencing
NewContentElementWizardHookInterfacethat no longer exists (for compatibility with older versions in a Hook).So it can’t really be fixed by only installing typo3/cms-report.
A downgrade of that symfony dependency was necessary.
Greetings
lps