-
Notifications
You must be signed in to change notification settings - Fork 39
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
Uncaught BadMethodCallException: Cannot serialize Symfony\Component\Routing\CompiledRoute when writing a log in a middleware. #136
Comments
This is caused because the |
+1 also get this problem whenever an error gets reported...
|
This is in latest Laravel 9.x, PHP 8.0.x |
Hmm... this is a problem. Give me a bit to work on a solution. |
I'm encountering this issue as well, but inconsistently. On one of our staging environments, we're seeing this occur specifically if an uncaught exception occurs. However, all of my attempts to trigger this same condition locally (including triggering the same underlying exceptions that are being caught) does not work - it seems as if the |
This issue prevents us from deploying L9 to production, is there any update or roadmap when we can expect a fix? |
@roelVerdonschot I'm in the same boat, there's a bit of discussion happening on rollbar/rollbar-php#567, which is where I've been watching for updates. |
Hi,
I got this error after upgrading to Laravel 9.
It happens when writing a log (or an error) message in a Laravel middleware.In Symfonys CompiledRoute the serialization is blocked:
Since it only happens during a middleware exception,I thought it's more related to Laravel. I can also report it to the rollbar/rollbar-php package.I just run a fresh composer update on all packages.
// edit:
It's not middleware related. It happens on any exception or log message everywhere.
The text was updated successfully, but these errors were encountered: