Xavi Subirà

Could you please refer explicity in the subject terms like "allow" or "shield.conf"? I was near to report same issue. Thanks a lot

Checking out 2.1.0 has "broken" my SF2 application cache. Is there any known bug or unexplicited behaviour behind 2.1.x? I think I've found a bug, motivated by "gos/web-socket-bundle", i'll bring...

Whenever I rebuild SF2 project cache via `php app/console cache:clear` it produces following constructor signature for class `Gos\Bundle\WebSocketBundle\Server\Type\WebSocketServer` ([at version 1.8.8](https://github.com/GeniusesOfSymfony/WebSocketBundle/blob/v1.8.8/Server/Type/WebSocketServer.php)) when warming up `app/cache/prod/appProdProjectContainer.php` ```php class GosBundleWebSocketBundleServerTypeWebSocketServer_000000004ee6d98f0000000078e37539e77e8ca7c8cf8b427c73c477d767db6e extends \Gos\Bundle\WebSocketBundle\Server\Type\WebSocketServer...

I think I've found. `symfony/proxy-manager-bridge` vendor has following "composer.json" requirements: ```json "require": { "php": ">=5.3.9", "symfony/dependency-injection": "~2.3", "ocramius/proxy-manager": "~0.4|~1.0|~2.0" }, "require-dev": { "symfony/config": "~2.3" }, ```

¿Really? Then, it is **not an issue** for "ocramius/proxy-manager", "symfony/proxy-manager-bridge" neither "zenframework/zend-code". Sorry for the inconvenience

Is this (kind of error), it happens at execution time ```log PHP Fatal error: Declaration of GosBundleWebSocketBundleServerAppDispatcherTopicDispatcher_000000004b5242aa000000002a3c5adfebd6ee0aa660f497e7e72cab75be4d85::dispatch($calledMethod, Ratchet\ConnectionInterface $conn, Ratchet\Wamp\Topic $topic, Gos\Bundle\WebSocketBundle\Router\WampRequest $request, $payload = NULL, $exclude = NULL, $eligible...

Sorry, cause I'm dealing with two interactions facing this problem. The error I've pasted [here](https://github.com/Ocramius/ProxyManager/issues/371#issuecomment-299415673) appears when clearing and warming up SF2 cache. And the initial [issue experienced](https://github.com/Ocramius/ProxyManager/issues/371#issuecomment-299406332) was reported...

Well, it ain't exactly what was told here https://github.com/Ocramius/ProxyManager/issues/371#issuecomment-299243386 BUT, Upgrading to `2.1.x` from `2.0.4`, meant assuming an upgrade from Zend Engine `3.0.0` to `3.0.1 (`php-cli `7.0.X` to `7.1`). My...

I confirm aligning both php interpreters to version 7.1 fixes the "error"

Recovering the issue subject, now that I have the project working (with ocramius/proxy-manager set at version `2.1.1`), I'm getting this error: > [2017-05-05 13:31:54] request.CRITICAL: Uncaught PHP Exception ReflectionException: "Class...