Strange routes behaviour in production
I have a strange routes behaviour in my production deployment with two panels, one "/admin" and one "/app".
On my local environment everything works expected, but on production it doesn't. If I log into /admin, everything is okay, if I try to login into /app, there are "too many redirects". I can't figure out, why.
If I run
php artisan route:list I get the correct routes in local, but there's a strange route in production deployment (ploi.io), which I think that causes the problem. I've created the custom LoginResponse recommended by Povilas (https://laraveldaily.com/post/filament-disable-dashboard-auto-redirect-url-after-login), but this doesn't solve the problem. Where does this "filament.app.home" route come from?
Of course, I've tried to delete the routes cache (and other caches), but nothing helped.Solution:Jump to solution
I found the problem: the installation of a new panel caused an error in the created AppPanelProvider.
->discoverPages(in: app_path('Filament/App/Pages'), for: 'App\\Filament\\App\\Pages') had a lowercase "/app/" and "\app\" instead of "/App/" and "\App\". It's really strange, but correcting that fixed my problem.2 Replies
Just realized, that there are some routs missing in production, too. That's really annoying... can anyone help me, please?
Solution
I found the problem: the installation of a new panel caused an error in the created AppPanelProvider.
->discoverPages(in: app_path('Filament/App/Pages'), for: 'App\\Filament\\App\\Pages') had a lowercase "/app/" and "\app\" instead of "/App/" and "\App\". It's really strange, but correcting that fixed my problem.