Laravel 5 on php artisan config:clear generated Closure::__set_state() error

Question

My code in on production and I ran

php artisan config:clear

After that, my code was not running. The index pages and all other pages went white screen and gave 500 internal server error in firebug. When I tried to run

php artisan

it gave me error as

PHP Fatal error:  Call to undefined method Closure::__set_state() in /var/www/live/vendor/config.php on line 56

My code is in production!! /vendor/config.php file was not present before, what happened with that code?? Have you faced any such error? I had given all permissions to storage/ folder and vendor/. Any help/guide would be much appreciated.

geckob · Answer 1 · 2016-09-21T14:19:19.573

31

I had similar issues when I ran php artisan config:cache. Apparently, it is an issue when the application is trying to load cached configuration files that have closures in it. It won't be fixed in Laravel since it is a bad practice to have closures in config files. Refer this Github issue

The way I solved this is by undo-ing this.

Delete the cache for config.

It is located in here

bootstrap/cache/config.php

OR

vendor/config.php

edited Sep 21 '16 at 14:19

answered Sep 21 '16 at 13:28

geckob

7,680
5
30
39

I'm not sure that this adds anything to the Answer that I posted two weeks earlier (but maybe I'm wrong, given the upvotes). Just sayin'. :) – Ben Johnson Oct 19 '17 at 16:08
[@Ben Johnson](https://stackoverflow.com/users/1772379/ben-johnson) Honestly, I think his answer was formatted so you could get to the solution faster. I am upvoting your answer too because you put in a little more effort :-) – yardpenalty.com Mar 09 '19 at 23:01

score 24 · Accepted Answer · answered Jul 03 '15 at 10:00

24

I had faced the similar issue in past don't know what caused it but as of now you can delete the config.php from /vendor it won't break your code.

And your code will be start working..

answered Jul 03 '15 at 10:00

Jaimin

872
6
15

3

This solution is just for one time, when you run the code `php artisan config:cache` the 2nd time it will pop up the error again – Mahmoud Kassem Jan 08 '18 at 02:28

score 8 · Answer 3 · answered Sep 06 '16 at 17:23

Among other root-causes, this error results from calling php artisan config:cache when a closure is defined inside any configuration file that Laravel attempts to load. Laravel does not allow for closures in configuration files; see:

https://github.com/laravel/framework/issues/9625

Deleting the resultant cache file, usually located at bootstrap/cache/config.php, "fixes" the error.

The long-term solution is to eliminate closures from all configuration files. The problematic config file can be determined by inspecting the offending line, as mentioned in the error message.

If the offending file is third-party, it is best to open an issue with the library, so that the issue is fixed upstream.

score 7 · Answer 4 · edited Sep 23 '18 at 21:19

Here is what I did to solve it:

Go to /vendor/tymon/jwt-auth/src/config/config.php and replace the lines for storage and auth with:

'auth' => 'Tymon\JWTAuth\Providers\Auth\IlluminateAuthAdapter', 'storage' => 'Tymon\JWTAuth\Providers\Storage\IlluminateCacheAdapter'

Go to /bootstrap/cache/config.php and delete it
Run the following commands in order:
A) php artisan config/cache
B) php artisan jwt:generate
C) php artisan vendor:publish --provider="Tymon\JWTAuth\Providers\JWTAuthServiceProvider"

and that should do it!

score 4 · Answer 5 · answered Aug 10 '19 at 06:31

4

Try to remove the config.php from bootstrap/cache folder. It worked for me.

answered Aug 10 '19 at 06:31

giapnh

2,950
24
20

1

Super helpful! Thanks. I ran `mv bootstrap/cache/config.php bootstrap/cache/config_old.php` and then `php artisan config:clear` – Ryan Aug 12 '19 at 16:19

score 0 · Answer 6 · edited Oct 16 '22 at 13:54

0

Edit vendor\laravel\framework\src\Illuminate\Foundation\Support\Providers\RouteServiceProvider.php:108 and delete required.

edited Oct 16 '22 at 13:54

James Risner

5,451
11
25
47

answered Oct 10 '22 at 09:50

teddy 225

81
1

score -1 · Answer 7 · edited Feb 09 '16 at 14:30

-1

Changing the config.php file inside the vendor/tymon/jwt-auth/src/config to this

'auth' => Tymon\JWTAuth\Providers\Auth\IlluminateAuthAdapter::class`

and this

'storage' => Tymon\JWTAuth\Providers\Storage\IlluminateCacheAdapter::class`

before runnning php artisan config:cache worked for me.

edited Feb 09 '16 at 14:30

cchapman

3,269
10
50
68

answered Feb 09 '16 at 14:10

Omar Abu Elyazeed

11
1

When you update JWT, the problem is solved with your answer. Thanks a lot! – pablorsk Oct 23 '17 at 22:58

score -1 · Answer 8 · answered Jun 19 '19 at 15:23

-1

solved using

composer update

composer install

answered Jun 19 '19 at 15:23

Saurabh Mistry

12,833
5
50
71

Laravel 5 on php artisan config:clear generated Closure::__set_state() error

8 Answers8

Linked

Related