Help Needed: Unexpected Behavior in Laravel Filament with APP_DEBUG=true
I'm encountering an issue with Laravel Filament not functioning as expected on my local development setup using Herd. I'm currently using the latest versions of Laravel 11 and Filament 3. The problem persists with APP_DEBUG=true
6 Replies
I got similar issue, i believe that it is related to https handling .
I tried using the website without SSL, but it still didn't work. I think the problem might be more about how Livewire and Nginx are set up.
Ensure you access the website through the domain exactly as listed in your .env and try agian.
checked no issue with domain name with same protocol(https)
I noticed something that might be causing the problem. When the "app_debug" setting is set to true, the program loads '/livewire/livewire.js'. But when it's set to false, it loads '/livewire/livewire.min.js'.
I'm not sure if this is what's causing the issue though.
livewire: https://github.com/livewire/livewire/blob/14d59b01c7100de8018121b4b6ccd3c965fafe4f/src/Mechanisms/FrontendAssets/FrontendAssets.php#L20-L26
GitHub
livewire/src/Mechanisms/FrontendAssets/FrontendAssets.php at 14d59b...
A full-stack framework for Laravel that takes the pain out of building dynamic UIs. - livewire/livewire
Solution
fix after removing ""spatie/laravel-blade-comments" package