version 2.4.5 throws an error Twig_Error_Runtime
An exception has been thrown during the rendering of a template ("Object not found").
in favicon.png.base64 (line 1)
Log Dump:
[2018-03-03 12:58:56] php.CRITICAL: Uncaught Exception: An exception has been thrown during the rendering of a template ("Object not found"). {"exception":"[object] (Twig_Error_Runtime(code: 0): An exception has been thrown during the rendering of a template ("Object not found"). at /vendor/symfony/twig-bundle/Resources/views/images/favicon.png.base64:1, UnexpectedValueException(code: 0): Object not found at /vendor/symfony/twig-bridge/Extension/ProfilerExtension.php:48, Twig_Error_Runtime(code: 0): An exception has been thrown during the rendering of a template ("Object not found"). at /var/www/Busybee/templates/Default/style.html.twig:13, UnexpectedValueException(code: 0): Object not found at /vendor/symfony/twig-bridge/Extension/ProfilerExtension.php:48)"} []
Rolled back to 2.4.4 and no error.
I have this issue too. And it only occurs when I set
APP_ENV=dev
APP_DEBUG=1
in my Symfony 4 .env file.
the problem is this update
Updating twig/twig (v2.4.4 => v2.4.5): Downloading (100%)
I installed 2.4.4 again and the problem disappear
git bisect tells me that the commit 6ab5fe9b8fd52f810fd902652659605b5fcf39a9 of #2621 has caused this issue. /cc @lstrojny
Confirmed, had to rollback to 2.4.4 to make it disappear.
V2.4.5 crashes for me as well. Symfony 3.4.5 on a local dev machine.
The error says:
Twig_Error_Runtime
An exception has been thrown during the rendering of a template ("Notice: Undefined offset: 0").
Rolling back to 2.4.4 fixes the problem.
Have the same issue with Symfony v3.4.5 and twig v2.4.5.
(4/4) Twig_Error_Runtime
An exception has been thrown during the rendering of a template ("Object not found").
in favicon.png.base64 (line 1)
Any Updates?
Rolling back to 2.4.4 for now.
I am having the same issue on 2.4.5, as others has mentioned rolling back to 2.4.4 fixed the problem
Please test PR https://github.com/twigphp/Twig/pull/2645
1.35.2 and 2.4.6 are out and fixes this issue.
Most helpful comment
1.35.2 and 2.4.6 are out and fixes this issue.