-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[LiveComponent] Cannot assign null to property Symfony\UX\LiveComponent\Twig\TemplateMap::$map of type array #1961
Comments
Do you sometimes prune / delete your cache folder ? Or even with a CachePoolClearer maybe ? |
We use Ansistrano for deployment. It places new version of the project in a new directory (with empty cache folder), and then switches a symlink to this new folder. |
Do you warm the cache before the symlink ? The other possibility would be: do you change your APP_SECRET between deployments ? |
APP_SECRET never changes. We currently do not warm the cache before symlink. That might just fix the issue. |
Well, yes and no :) Yes it would work to "render" a component. But if you clear the cache (without rebuilding it) while a user is browsing a page containing live components, that would break. Maybe we should generate this file in the "build" directory and not the "cache" one ? |
Is there at least some workaround? It happens constantly in one app I create, only in the docker container, though. |
Hi @RikudouSage, do you have APP_SECRET env variable configured? |
@RikudouSage Maybe you should warm the cache before running the app ? |
Hi,
During deployment on our live environment we quite often get the error
Cannot assign null to property Symfony\UX\LiveComponent\Twig\TemplateMap::$map of type array
It seems to be related to a race condition with cache. Not sure how it occurs exactly, but it can easily be reproduced by deleting the
live_components_twig_templates.map
file from the cache folder.The text was updated successfully, but these errors were encountered: