I am getting this error now as well.
BadMethodCallException: Method Illuminate\Auth\RequestGuard::getRecallerName does not exist. in /var/task/vendor/laravel/framework/src/Illuminate/Macroable/Traits/Macroable.php:113
My experience is slightly different, though. I just used Laravel Shift to update from 8.x to 9.x. My app works fine for everyone who is already logged in, but when I tried a new login I got this error in my logging. The login attempt simply takes my back to the login page over and over again. When my credentials are wrong, it tells me they are wrong. But then sometimes I can login without issue and no errors are reported. Very strange. Any additional thoughts about what could be going on here?
Also, this error started showing up at the same time:
BadMethodCallException: Cannot serialize Symfony\Component\Routing\CompiledRoute in /var/task/vendor/symfony/routing/CompiledRoute.php:71
I am not sure if they are related. Here is the first few lines of the stack trace:
BadMethodCallException: Cannot serialize Symfony\Component\Routing\CompiledRoute in /var/task/vendor/symfony/routing/CompiledRoute.php:71
Stack trace:
#0 /var/task/vendor/rollbar/rollbar/src/Utilities.php(145): Symfony\Component\Routing\CompiledRoute->serialize()
#1 /var/task/vendor/rollbar/rollbar/src/Utilities.php(105): Rollbar\Utilities::serializeObject(Object(Symfony\Component\Routing\CompiledRoute), NULL, Array, -1, 2)
#2 /var/task/vendor/rollbar/rollbar/src/Utilities.php(159): Rollbar\Utilities::serializeForRollbar(Object(Illuminate\Routing\Route), NULL, Array, -1, 2)
#3 /var/task/vendor/rollbar/rollbar/src/Utilities.php(105): Rollbar\Utilities::serializeObject(Object(Illuminate\Routing\Route), NULL, Array, -1, 1)
#4 /var/task/vendor/rollbar/rollbar/src/Utilities.php(117): Rollbar\Utilities::serializeForRollbar(Array, NULL, Array, -1, 1)
It looks like an issue with Rollbar (my error reporting system) not Laravel. But I thought I'd mention it because in my upgrade to 9.x, Shift said I needed to run
composer require symfony/mailgun-mailer symfony/http-client
because Laravel 9 transitioned from SwiftMailer to Symfony Mailer. While this transition should be relatively seamless and Shift automates any tedious changes, there are some changes which are not reliably automated. And now I'm getting an error in Symfony.