Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1

Question

Loading composer repositories with package information Updating dependencies (including require-dev) Package operations: 0 installs, 0 updates, 1 removal - Removing genealabs/laravel-caffeine (0.3.12) Writing lock file Generating optimized autoload files

Illuminate\Foundation\ComposerScripts::postAutoloadDump @php artisan package:discover

[Symfony\Component\Debug\Exception\FatalThrowableError]
Class 'GeneaLabs\LaravelCaffeine\LaravelCaffeineServiceProvider' not found

just run `composer update` to install the required packages ,Check [this](https://github.com/GeneaLabs/laravel-caffeine/issues/44) — Neji Soltani, Oct 28 '17 at 03:42
I occasionally get this error, so far I've found that simply executing the command again works. `composer dump autoload` — liamvictor, Mar 12 '19 at 10:30
@liamvictor I believe you meant to say `composer dump-autoload`, just in case anyone comes across this. — Colin, May 14 '20 at 18:49
That's worked for me. Running the command **php artisan package:discover --ansi** by itself might tell you more about the issue. — MsM Robin, Jun 21 '21 at 09:44
this command is very helpful to find out the actual cause. @MsMRobin thanks — Moaz Ateeq, Aug 23 '21 at 17:41

score 65 · Answer 1 · answered Oct 16 '19 at 20:04

65

I simply ran composer update and it resolved my issue - Laravel 6.*

answered Oct 16 '19 at 20:04

BE KNOW DO

783
5
6

6

This should be the accepted answer - dont fiddle with files just update the composer and it does it for you... works like a charm. – alex toader Nov 10 '20 at 09:58
4

This is the correct answer, it worked for me based on the same error – kamau wairegi Jan 20 '21 at 18:39
2

I receive this message already at the end of the ```composer update``` command. So, running it again doesn't solve the problem. – mdikici Nov 29 '21 at 12:35
Works like a charm bro! Thanks for this! – Jhune Carlo Trogelio Jan 05 '22 at 04:42
composer update did the trick – Sudhanshu Garg Jan 19 '22 at 04:57
I still getting the same error after running composer update command – Ariful Islam Feb 02 '22 at 10:28
It's not working in my case. Gives another problem. – Nijat Mursali Nov 13 '22 at 13:36

score 34 · Accepted Answer · edited Mar 24 '18 at 18:44

34

Add this in composer.json. Then dusk has to be installed explicitly in your project:

"extra": {
    "laravel": {
        "dont-discover": [
            "laravel/dusk"
        ]
    }
},

I found this solution here

edited Mar 24 '18 at 18:44

SevenEleven

2,326
2
32
32

answered Mar 24 '18 at 17:41

Abed Bilani

614
6
7

1

tried it, didn't solve for me – ronapelbaum Jan 09 '22 at 10:32

score 23 · Answer 3 · answered Sep 14 '18 at 23:44

23

In case you're coming from a google search, make sure that you have a .env file in which APP_ENV is set to local. (if you cloned a project from github, the first thing is to run cp .env.example .env. That was actually the problem in my case)

Then run composer install again.

answered Sep 14 '18 at 23:44

Itope84

471
5
7

This solves the problem for me. The **.env** is replaced by .env.example for project from GitHub. So we need to create it using the **.env.example** by running the command **cp .env.example .evn** . The command us just copying the **.env.example** and set it name by **.env** – stic-lab Jan 30 '22 at 08:57

score 6 · Answer 4 · edited Nov 18 '18 at 07:32

You have added the service provider in config/app.php for the package that is not installed in the system.

You must have this line in your config/app.php. You can either remove it or install the package GeneaLabs\LaravelCaffeine\LaravelCaffeineServiceProvider

See https://github.com/GeneaLabs/laravel-caffeine.

Run the line below via CLI to install the package.

 composer require genealabs/laravel-caffeine

score 4 · Answer 5 · answered Aug 24 '19 at 08:36

My problem was fideloper proxy version.

when i upgraded laravel 5.5 to 5.8 this happened

just sharing if anybody get help

change you composer json fideloper version:

"fideloper/proxy": "^4.0",

After that you need to run update composer that's it.

composer update

score 4 · Answer 6 · answered Apr 23 '20 at 08:06

4

In case the error appears when upgrading from Laravel 6 to Laravel 7, the command composer require laravel/ui "^2.0" solves the problem (see https://laravel.com/docs/7.x/upgrade#authentication -scaffolding)

answered Apr 23 '20 at 08:06

robotu

203
2
7

score 4 · Answer 7 · answered Mar 14 '21 at 01:14

4

Running the command php artisan package:discover --ansi by itself might tell you more about the issue. In my case correcting a character out of place in the .env solved it.

answered Mar 14 '21 at 01:14

hmg

186
1
7

1

This is weird the exact same case happen to both of us the same DAY, in my case it was a character in my passport tokens declaration – Danys Chalifour Mar 14 '21 at 18:02

score 3 · Answer 8 · answered May 03 '20 at 09:37

3

This happened to me because I had a ddd() or dd();die; in my routes/web.php file I forgot about.

answered May 03 '20 at 09:37

Joe

427
1
6
16

Thanks! I had a dd on AppServiceProvider – Lucas Nov 28 '20 at 08:22

score 3 · Answer 9 · answered Sep 08 '20 at 22:38

3

In my case, I had left over references to classes in a recently removed composer package. In your laravel app, check config/app.php, particularly the providers and aliases properties, for references to the class specified in the error.

answered Sep 08 '20 at 22:38

user3561812

69
3

score 3 · Answer 10 · answered Oct 25 '20 at 13:51

3

I needed rollback for the 1.9.x version, in 2.x.x not work

composer self-update --rollback

answered Oct 25 '20 at 13:51

Diogo Machado

396
2
11

This was the cause of my issue. A deploy script that installed composer into the current folder if composer was not already on the system installed a 2.0.x version of composer. – Jim OHalloran Dec 14 '20 at 06:19

score 3 · Answer 11 · answered Jun 21 '22 at 13:13

3

You could try

composer update

That worked for me when I had this same issue. In my case what made me discover this issue was when i tried to run the artisan command and it didn't return anything

So I tried composer dumpautoload which threw me this same error mentioned

composer update did the trick

answered Jun 21 '22 at 13:13

Daniel Mabadeje

41
1
4

In my case this was it, thanks – Jairo Nava Magaña Sep 13 '22 at 16:44

score 2 · Answer 12 · answered Mar 03 '20 at 04:14

2

I came across this when upgrading from 5.8 to 6.x.

I had str_slug() in config/cache.php and config/session.php.

I have changed it to Str::slug() and the error has disappeared.

See https://laravel.com/docs/6.x/upgrade#helpers.

answered Mar 03 '20 at 04:14

Roman Grinyov

222
2
5
20

score 2 · Answer 13 · answered May 31 '20 at 17:50

in this case, I use space for APP_NAME key in .env file.

and have below error :

The environment file is invalid!
Failed to parse dotenv file due to unexpected whitespace. Failed at [my name].
Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1

Don't use space in APP_NAME key !!

score 2 · Answer 14 · answered Mar 21 '21 at 09:13

2

Just Remove bootstrap/cache/config.php file. then it works fine

answered Mar 21 '21 at 09:13

Keshab Pal

31
3

Then after composer dump-autoload – Keshab Pal Mar 21 '21 at 09:14
1

Please [edit your answer](https://stackoverflow.com/posts/66730584/edit) instead of adding a new comments. – Syscall Mar 21 '21 at 09:47
1

In my case I was trying to remove a package but forgot to remove it from config/app.php providers section hence, the error and this results to being unable to run php artisan and/or composer dumpautoload. Remove bootstrap/cache/config.php file then run composer dumpautoload again. After that php artisan works again just fine. – Dale Ryan Nov 05 '21 at 03:52

score 2 · Answer 15 · answered Oct 18 '21 at 08:38

2

My solution was creating the storage/framework/cache/data/cache folder and gave it permissions

answered Oct 18 '21 at 08:38

STREET MONEY

534
4
8

1- add all directories in cache directory "storage\framework\cache\data\cache" 2- Remove bootstrap/cache/config.php file. 3- remove incorrect syntax of .env file – Anas Alpure Jan 27 '22 at 19:48

score 1 · Answer 16 · answered Sep 22 '21 at 18:01

1

Just run composer update it will solve the issues.

answered Sep 22 '21 at 18:01

Lawrence E Bosumbe

488
7
16

this fixed my issue , thanks – mahmudy-91 Mar 03 '22 at 12:55

score 1 · Answer 17 · answered Apr 20 '22 at 19:20

In my case this error happened to me when i removed a package with composer remove, then i realized somehow, something affected my config files in config directory, and they all become empty.

Solution for me was simply getting those files from Laravel repository and copy them into config directory. (and of course in case you need to do vendor publish for specific libraries, you should do it again.)

Zack Morris · Answer 18 · 2020-11-30T18:37:06.883

If none of the solutions work for you, the handling the post-autoload-dump event returned with error code 1 error can also be caused by using Composer 2 instead of Composer 1. That can happen when you run the install command manually in something like a Dockerfile, and it installs newest. Just modify your command to install the last 1.x.x stable version with the --1 option:

curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer --1

Or, specify a certain version with --version=x.x.x:

curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer --version=1.10.17

It might be good to also delete your vendor directory and composer.lock file so that nothing stale interferes with the version downgrade, before calling composer install as usual.

score 0 · Answer 19 · answered Jan 31 '21 at 15:15

in my case the problem was into outdated "../bootstrap/cache/packages.php and services.php"

I have had to. drop those files and rerun composer install...

  Erroneous data format for unserializing 'Symfony\Component\Routing\CompiledRoute'


Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1

score 0 · Answer 20 · edited Feb 10 '21 at 13:39

I have same issue

above this error

Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1

I found one more message in my terminal like: "

"Cartalyst\Stripe\Laravel\StripeServiceProvider::class, not found in your ProviderRepository.php"

then i go config/app.php and find

Cartalyst\Stripe\Laravel\StripeServiceProvider::class

comment it out then run

composer update

it will work fine **In your case maybe package name is different please check your terminal **

score 0 · Answer 21 · answered May 20 '21 at 03:05

in my case this was the error

> @php artisan package:discover --ansi

In AuthServiceProvider.php line 29:

  syntax error, unexpected '=>' (T_DOUBLE_ARROW), expecting ')'


Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

I solved it by upgrading PHP version to 7.4

because i was using Arrow functions in the AuthServiceProvider that came up in 7.4

score 0 · Answer 22 · answered May 26 '22 at 01:53

0

step 1: create .env file

step 2: create storage folders and sub folder

step3: run command composer install again

answered May 26 '22 at 01:53

Đọc truyện hay

1,913
21
17

score 0 · Answer 23 · answered Dec 02 '22 at 17:45

0

If composer update and composer install not work then you can try this composer require laravel/sanctum

answered Dec 02 '22 at 17:45

Bipu

11
4

score 0 · Answer 24 · answered Dec 23 '22 at 08:28

0

Please check first artisan file present in root folder and this error is occurred because some file is missing from your project, download new laravel project and check all files with your existing project

answered Dec 23 '22 at 08:28

Ajay

1
1

score 0 · Answer 25 · answered Apr 05 '23 at 19:26

0

if you cloned a project from github, the first thing is to run cp .env.example .env.

Then run composer install again.

That was actually the problem in my case

this is idea from @Itope84

answered Apr 05 '23 at 19:26

Kuncing

1
1

score -1 · Answer 26 · answered Mar 13 '19 at 12:04

-1

Check your code for errors in my case i had an error in Kernel.php. First solve errors if any Than run composer require ....(package you wish)

answered Mar 13 '19 at 12:04

Yllndrit

57
6

score -2 · Answer 27 · answered Nov 28 '20 at 17:06

-2

remove the config.php file located in bootstrap/cache/ enter link description here

that's works with me

answered Nov 28 '20 at 17:06

Abdullah Alamodi

129
1
7

Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1

27 Answers27

Linked

Related