Exception handle with custom views not working correctly

[melvinmihaylovnulabg]

Package

filament/filament

Package Version

v3.2.115

Laravel Version

v10

Livewire Version

v3

PHP Version

PHP 8.2

Problem description

When using custom views for handing exceptions like 403, 404, 419, 500 on the main website ( the website was build with laravel blade components, then filamentphp admin panel was implemented on top of that for admin panel ) and for example if the session of the user expires in the filamentphp admin panel the user gets the custom error blade embedded in the filament admin panel with 419 error code.

Expected behavior

Show filament's pages for these kinds of errors.

Steps to reproduce

login in the admin panel, delete sessions in the database, wait a little bit in the admin panel and then the alert pops up with the message and the page shows 419 error message embedded.

Reproduction repository (issue will be closed if this is not valid)

https://github.com/filamentphp/filament

Relevant log output

No response

Donate 💰 to fund this issue

• You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
• 100% of the funding will be distributed between the Filament core team to run all aspects of the project.
• Thank you in advance for helping us make maintenance sustainable!

[github-actions]

Hey @melvinmihaylovnulabg! We're sorry to hear that you've hit this issue. 💛

However, it looks like you forgot to fill in the reproduction repository URL. Can you edit your original post and then we'll look at your issue?

We need a public GitHub repository which contains a Laravel app with the minimal amount of Filament code to reproduce the problem. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private / confidential, since we want a link to a separate, isolated reproduction. That would allow us to download it and review your bug much easier, so it can be fixed quicker. Please make sure to include a database seeder with everything we need to set the app up quickly.