<p dir="auto">Hi there,</p>
<p dir="auto">I am in the process of upgrading a Silex app and part of that is an upgrade of the sf components. With sf 2.6 I've run into a problem with the TraceableEventDispatcher.<br>
Dispatcher version is v2.6.6</p>
<p dir="auto">silex_upgrade/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Session/Storage/MockArraySessionStorage.php:134<br>
silex_upgrade/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Session/Session.php:199<br>
silex_upgrade/vendor/silex/silex/src/Silex/Provider/SessionServiceProvider.php:93<br>
silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/Debug/WrappedListener.php:61<br>
silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/Debug/WrappedListener.php:61<br>
silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/EventDispatcher.php:164<br>
silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/EventDispatcher.php:53<br>
silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/Debug/TraceableEventDispatcher.php:112<br>
silex_upgrade/vendor/symfony/http-kernel/Symfony/Component/HttpKernel/HttpKernel.php:126<br>
silex_upgrade/vendor/symfony/http-kernel/Symfony/Component/HttpKernel/HttpKernel.php:66<br>
silex_upgrade/vendor/silex/silex/src/Silex/Application.php:543<br>
silex_upgrade/vendor/symfony/http-kernel/Symfony/Component/HttpKernel/Client.php:81<br>
silex_upgrade/vendor/symfony/browser-kit/Symfony/Component/BrowserKit/Client.php:327<br>
silex_upgrade/php/tests/controllers/TestLookupController.php:20</p>
<table role="table">
<thead>
<tr>
<th>Q</th>
<th>A</th>
</tr>
</thead>
<tbody>
<tr>
<td>Bug report?</td>
<td>yes</td>
</tr>
<tr>
<td>Feature request?</td>
<td>no</td>
</tr>
<tr>
<td>BC Break report?</td>
<td>no</td>
</tr>
<tr>
<td>RFC?</td>
<td>no</td>
</tr>
<tr>
<td>Symfony version</td>
<td>3.2.1</td>
</tr>
</tbody>
</table>
<p dir="auto">After upgrading to PHP 7.1 and symfony 3.2.1 I sometimes (once a week, random) get the following error:</p>
<blockquote>
<p dir="auto">FatalErrorException in classes.php line 347:<br>
Error: Class Symfony\Component\HttpFoundation\Session\Storage\Proxy\SessionHandlerProxy contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (SessionHandlerInterface::write)</p>
</blockquote>
<p dir="auto">I changed the following lines in config.yml to the new Symfony 3 style:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="session:
        # handler_id set to null will use default session handler from php.ini
        handler_id:  session.handler.native_file
        save_path:   &quot;%kernel.root_dir%/../var/sessions/%kernel.environment%&quot;"><pre class="notranslate"><code class="notranslate">session:
        # handler_id set to null will use default session handler from php.ini
        handler_id:  session.handler.native_file
        save_path:   "%kernel.root_dir%/../var/sessions/%kernel.environment%"
</code></pre></div>
<p dir="auto">But it still happened.</p>
<p dir="auto">After reading <a href="http://stackoverflow.com/questions/36088683/php-7-symfony-3-fatal-error-1-abstract-method-and-must-therefore-be-declared-a" rel="nofollow">http://stackoverflow.com/questions/36088683/php-7-symfony-3-fatal-error-1-abstract-method-and-must-therefore-be-declared-a</a><br>
The solution is indeed to restart Apache.</p>
<p dir="auto">I have no clue what can be the cause, maybe PHP 7.1, but Symfony 3 is compatible with 7.1 right?</p>
<p dir="auto">Maybe someone here can point me in the right direction to solve this :)</p>