Upgrade to Components! 3.0.0-beta3 breaks website

That service is no longer called. Did you run database updates and clear cache?
I just updated this module on one of the sites I manage, before running updates and clearing cache I got the same error.
After running db updates and clearing cache the site loads as expected.

Please confirm this works.

Wanted to chime in that I have the same issue. N.B. db updates/cache clear do not resolve the problem.

For context, this is running on a site using D9.5.7 as I prepare for migration to D10.

I normally clear cache and update DB from the admin UI. This is not possible after upgrade to Components! 3.0.0-beta3, because the website is broken. So, I did the DB update with drush, but I got no system prompt back after 3 updates (and killed the proces with :

pi@pi3:/var/www/pi3.softpol.net $ vendor/bin/drush updatedb
------------ ---------------- ------------- ---------------------------------
Module Update ID Type Description
------------ ---------------- ------------- ---------------------------------
components components_reg post-update Clear caches to allow
istry_cache_pa components.registry service to
ths cache template paths.
components components_reg post-update Clear caches to load new
istry_service components.registry service.
components components_twi post-update Clear caches to load updated
g_loader_servi components.twig.loader service.
ce
------------ ---------------- ------------- ---------------------------------

Do you wish to run the specified pending updates? (yes/no) [yes]:
>

> [notice] Update started: components_post_update_components_registry_cache_paths
> [notice] Update completed: components_post_update_components_registry_cache_paths
> [notice] Update started: components_post_update_components_registry_service
> [notice] Update completed: components_post_update_components_registry_service
> [notice] Update started: components_post_update_components_twig_loader_service
> [notice] Update completed: components_post_update_components_twig_loader_service

^C

I then did a clear cache with drush:

pi@pi3:/var/www/pi3.softpol.net $ vendor/bin/drush cache-rebuild
[success] Cache rebuild complete.

and retried the DB update. AFter a long wait, I got a bunch of error messages, ending with:

PHP Fatal error: Uncaught Symfony\Component\Routing\Exception\RouteNotFoundException: Route "" does not exist. in /var/www/pi3.softpol.net/web/core/lib/Drupal/Core/Routing/RouteProvider.php:206
Stack trace:
#0 /var/www/pi3.softpol.net/web/core/lib/Drupal/Core/Routing/UrlGenerator.php(432): Drupal\Core\Routing\RouteProvider->getRouteByName()
#1 /var/www/pi3.softpol.net/web/core/lib/Drupal/Core/Routing/UrlGenerator.php(270): Drupal\Core\Routing\UrlGenerator->getRoute()
#2 /var/www/pi3.softpol.net/web/core/lib/Drupal/Core/Render/MetadataBubblingUrlGenerator.php(105): Drupal\Core\Routing\UrlGenerator->generateFromRoute()
#3 /var/www/pi3.softpol.net/web/core/lib/Drupal/Core/Url.php(765): Drupal\Core\Render\MetadataBubblingUrlGenerator->generateFromRoute()
#4 /var/www/pi3.softpol.net/web/modules/contrib/visitors/src/EventSubscriber/KernelTerminateSubscriber.php(152): Drupal\Core\Url->toString()
#5 [internal function]: Drupal\visitors\EventSubscriber\KernelTerminateSubscriber->onTerminate()
#6 /var/www/pi3.softpol.net/web/core/lib/Drupal/Component/EventDispatcher/ContainerAwareEventDispatcher.php(142): call_user_func()
#7 /var/www/pi3.softpol.net/vendor/symfony/http-kernel/HttpKernel.php(103): Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch()
#8 /var/www/pi3.softpol.net/vendor/stack/builder/src/Stack/StackedHttpKernel.php(32): Symfony\Component\HttpKernel\HttpKernel->terminate()
#9 /var/www/pi3.softpol.net/web/core/lib/Drupal/Core/DrupalKernel.php(702): Stack\StackedHttpKernel->terminate()
#10 /var/www/pi3.softpol.net/vendor/drush/drush/src/Boot/DrupalBoot8.php(310): Drupal\Core\DrupalKernel->terminate()
#11 [internal function]: Drush\Boot\DrupalBoot8->terminate()
#12 {main}
thrown in /var/www/pi3.softpol.net/web/core/lib/Drupal/Core/Routing/RouteProvider.php on line 206

But eventually the website was again up…

I don't know if I applied the right commands, or in the right order. It would be good to add some additional instructions to the upgrade procedure.

That is documented here: https://www.drupal.org/docs/updating-drupal/updating-drupal-core-via-com... →
Generally though you want to run drush updb first then clear cache.

Unfortunately what I suspect is happening is that the pi was just running out of memory trying to run the updates. I'm glad you were able to get it working though.

I can confirm that. In my case running drush cr right after I upgraded from Components 8.x-2.4 to version 3.0.0-beta3 broke the whole site und crashed it's Docker container.

In a second attempt I ran drush updb before clearing the caches. This time I succeeded.