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

Question

I got some weird error code after I pulled a project out of my github. My first things I do is composer dumpautoload, composer update, and php artisan migrate:fresh --seed whenver I get to a new terminal. This time, I'm stuck at dumpautoload as it generates this error.

Here's what composer update generated

Loading composer repositories with package information
The "https://repo.packagist.org/packages.json" file could not be downloaded: SSL: An existing connection was forcibly closed by the remote host.

send of 158 bytes failed with errno=10054 An existing connection was forcibly closed by the remote host.

failed to open stream: HTTP request failed! 
https://repo.packagist.org could not be fully loaded, package information was loaded from the local cache and may be out of date
Updating dependencies (including require-dev)
Nothing to install or update
Writing lock file
Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi
Discovered Package: awobaz/compoships
Discovered Package: facade/ignition
Discovered Package: fideloper/proxy
Discovered Package: intervention/image
Discovered Package: laravel/tinker
Discovered Package: laravel/ui
Discovered Package: maatwebsite/excel
Discovered Package: nesbot/carbon
Discovered Package: nunomaduro/collision
Discovered Package: spatie/laravel-medialibrary
Discovered Package: yajra/laravel-datatables-oracle
Package manifest generated successfully.
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error
code -1073741819

Lift

try php artisan clear and see what error you get so you know what file is causing the error – Senhor

execute php artisan clear – Manhood

execute php artisan dump-autoload to clear all logs – Mulry

All didnt work, produced the same error code. – Lift

When you try to execute php artisan migrate:fresh --seed your data in the database will be lost. Make sure on that point before use – Liber

@MangalaKarunarathne this was a development project in 2020, and yes I do fresh and seed on a local server – Lift

Answer 1

Old (cached) local dependencies or composer.lock file may causes problem like this. You can try to reinstall all dependencies after remove all dependencies and lock file.

To remove downloaded dependencies, execute this inside app base dir;

sudo rm -rf vendor/

after that delete composer.lock file by executing;

sudo rm composer.lock

and finally execute;

composer install

Vesper

took me a year to understand this sets of code. I work on a Windows platform and the first thing when I saw this last year was why it doesnt work on the command line – Lift

I have been searching for a sol for months. This worked for me. – Ullund

this solution make sense – Singlehandedly

Answer 2

To resolve this, configure composer to use the https repository by running the following command on the cli before installing Laravel

composer config -g repo.packagist composer https://packagist.org

Manhood

First didn't work. Second, was using local already. Last, also didn't work. – Lift

Now you added the composer error. To solve this run composer config -g repo.packagist composer https://packagist.org – Manhood

the repo was fixed but the post-autoload-event persists – Lift

if you cloned a project from github, the first thing is to run cp .env.example .env Then run composer install again – Manhood

Also check the content of config/databse.php – Manhood

Answer 3

Just delete the vendor directory and install the composer again composer install

Liber

Answer 4

Try to create a new laravel project, and use the new files under the storage/ & bootstrap/cache to replace the files in the original folders.

Celtuce

Answer 5

I had the same issue and tried re-establishing the dependancies but this did not work for me. It turned out that it was the DB schema causing the issue. More specifically - I had a legacy table named settings. Once I renamed this table and followed up with composer install, the problem was solved. I think this is due to a spatie package that creates a settings table for itself.

Esquivel

Answer 6

For me, I had to run this command: mkdir -p bootstrap/cache. Basically, create this folder in order for it to run.

Croydon