Filament notification 500 error

I am working with Filament v3 and Laravel v12. Whenever a Filament notification is created, it throws 500 error and stop the project. Even if I try to run the project again, it will still throw the 500 error. Only after I clear the sessions table or generate a new app_key, the project run again. This happens when I submit any form and filament try to create "Successfully" notification or when I manually try to create filament notification "Notification:make()". Below are the things that I tried but didn't work: - changing SESSION_DRIVER to 'file'. - clearing cache or config - running composer install or update There is this error message in laravel.log and I already tried increasing memory_limit on php.ini. And I don't think there is any recursive or infinite loop function happening either because it was working at first and when I run composer update it starting happening like this. I also tried making a new filament project and it also happens in the new project: Allowed memory size of 536870912 bytes exhausted (tried to allocate 131072 bytes) {"userId":1,"exception":"[object] (Symfony\Component\ErrorHandler\Error\FatalError(code: 0): Allowed memory size of 536870912 bytes exhausted (tried to allocate 131072 bytes) at D:\Projects\web-apps\top-up-nation\storage\framework\views\1bb57ddc19d401c27a42741ae2b78db6.php:394)
Solution:
Update to the latest version and try again
Jump to solution
6 Replies
ChesterS
ChesterS3mo ago
Did this start happening recently? Update Filament to the latest version - there's a fix for a change introduced in Laravel 12 that leads to an infinite loop or something https://github.com/filamentphp/filament/pull/16878
shadowburnz
shadowburnzOP3mo ago
Yes, it started happening today
ChesterS
ChesterS3mo ago
The fix was for v3.3.31 what version are you on? (php artisan about --only=filament)
shadowburnz
shadowburnzOP3mo ago
I'm on version 3.3.0
Solution
ChesterS
ChesterS3mo ago
Update to the latest version and try again
shadowburnz
shadowburnzOP3mo ago
It is working now after updating to v3.3.31 as you suggested. Thank you. You are a life saver.

Did you find this page helpful?