title: Cannot load fixtures in Symfony 3.4
body: <p>I'm using the DoctrineFixturesBundle.  According to the <a href="https://symfony.com/doc/current/bundles/DoctrineFixturesBundle/index.html" rel="nofollow noreferrer">documentation</a>, any class that extends <code>Fixture</code> will be automatically wired up so the console knows how to handle it.  However, despite my fixtures class extending <code>Fixture</code> (code below), I keep getting the following error:</p>
  
  <blockquote>
    <p>Could not find any fixture services to load.</p>
  </blockquote>
  
  <p>If I attempt to wire up the service manually in my <code>services.yml</code> file with:</p>
  
  <pre><code>services:
      AppBundle\DataFixtures\:
          resource: '../../src/AppBundle/DataFixtures/'
          tags: ['doctrine.fixture.orm']
  </code></pre>
  
  <p>I instead get:</p>
  
  <blockquote>
    <p>In FileLoader.php line 168:</p>
    
    <p>The file "../../src/AppBundle/DataFixtures" does not exist (in: /path/to/project/app/config) in /path/to/project/app/config/services.yml (which is being imported from "/path/to/project/app/config/config.yml").                                                   </p>
    
    <p>In FileLocator.php line 71:</p>
    
    <p>The file "../../src/AppBundle/DataFixtures" does not exist (in: /path/to/project/app/config).</p>
  </blockquote>
  
  <p>The path to my data fixtures is <code>/path/to/project/src/DataFixtures</code>.  The actual class file (<code>AppFixtures.php</code>) is:</p>
  
  <pre><code>namespace AppBundle\DataFixtures;
  
  use AppBundle\Entity\Category;
  use AppBundle\Entity\Product;
  use Doctrine\Bundle\FixturesBundle\Fixture;
  use Doctrine\Common\Persistence\ObjectManager;
  
  class AppFixtures extends Fixture
  {
      public function load(ObjectManager $em)
      {
          $category = new Category();
  
          $category-&gt;setName("Test Category")
              -&gt;setSlug()
              -&gt;setDescription("This is only for test purposes");
  
          $fabricProduct = new Product();
  
          $fabricProduct-&gt;setName("Test OldProduct")
              -&gt;setCanonicalPrice(2.45)
              -&gt;setHasSale(false)
              -&gt;setCategory($category)
              -&gt;setSlug()
              -&gt;setNumberInStock(45.25);
  
          $em-&gt;persist($category);
          $em-&gt;persist($fabricProduct);
          $em-&gt;flush();
      }
  }
  </code></pre>
  
  <p>To preemptively answer the obvious questions, yes the bundle is registered correctly.  And my <code>services.yml</code> file has the default autowiring:</p>
  
  <pre><code>services:
      # default configuration for services in *this* file
      _defaults:
          # automatically injects dependencies in your services
          autowire: true
          # automatically registers your services as commands, event subscribers, etc.
          autoconfigure: true
          # this means you cannot fetch services directly from the container via $container-&gt;get()
          # if you need to do this, you can override this setting on individual services
          public: false
  </code></pre>
  
  <p>Any ideas on what I'm doing wrong?  According to all the documentation I've found, this should be working.</p>