-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Laravel 5.2 supported? #461
Comments
Could you post more details of how your environment/app is set up and which code block trigger this exception? I'm running |
Yes there's an issue with the config files because they relied on closures at one point but then Laravel officially dropped support. (#147 and many others) If you're on develop you'll just have to republish your vendor config for jwt-auth. If you're on master, just copy the provider classnames from the develop branch's config. @tymondesigns - Laravel 5.1/5.0 doesn't need the closures right? It was just 4.2? Cause then this should probably change before that 0.5 bugfix release... |
@tdhsmith oops, yea I forgot about this.. (it is laravel 5.1) I might make 0.5.8 now to remove closures from the config |
Awesome! I just peeked at 0.5.7 and wondered that. 😛 |
An example implementation for Laravel 5.2.x using the JWTGuard can be found at #513 |
Hello guys, actually laravel 5.2 supported?
PHP Fatal error: Call to undefined method Closure::__set_state() in /bootstrap/cache/config.php on line 543
The text was updated successfully, but these errors were encountered: