Do you have a class under Service-auto registration that uses entities as constructor parameters?

This is where your problem lies.

You need to ask yourself whether this related class is really a service, or just an ordinary object that you always create instances yourself.

If it is not used as a service through a container, you have two options:

You can exclude this class through a global pattern similar to the following:

AppBundle\:
    resource: '...'
    # 您可以排除目录或文件
    # 但如果一个服务未使用，它会被移除
    exclude: '../../{Entity,PathToYourNotService}'

Or you can set the following parameters in your configuration:

parameters:
    container.autowiring.strict_mode: true

With this option, the container will not try to create a service class with parameters that are not available as a service, and you will get a decisive error. This is the default setting for sf4.

A good example that triggers this error is a custom event class that takes an entity as a payload in the constructor:

namespace AppBundle\Event;

use AppBundle\Entity\Item;
use Symfony\Component\EventDispatcher\Event;

class ItemUpdateEvent extends Event
{
    const NAME = 'item.update';

    protected $item;

    public function __construct(Item $item)
    {
        $this->item = $item;
    }

    public function getItem()
    {
        return $this->item;
    }
}

Now, if this file is not specifically excluded, the container will attempt to automatically register it as a service. Since the solid body is excluded, it cannot be autowired. But in 3.4, there is this fallback mechanism that triggers this warning. Once strict_mode is activated, the event is not available as a service and will throw an error if you try to use it as a service.