framework: [5.5] Cannot clear package auto-discovery cache

@themsaid, composer dump-autoload do no solve this problem - after running you still have nonexistent provider classes inside bootstrap/cache/config.php and all artisan commands will fail. Moreover, seems this bug can be fixed only by hands with rm bootstrap/cache/config.php 😦

I think this should be reopened and fixed.

I agree with @LastDragon-ru, I went through same thing today, only rm bootstrap/cache/config.php solved the issue and has restored all commands.

Neither of these were working:

composer du
composer dump-auto
composer dump-autoload
composer install
composer update
composer remove old-package-name
php artisan cache:clear
php artisan config:clear
php artisan package:discover

All of them were showing Class 'XXX' not found.

How did I get there? I’ve installed a package (composer require package-name), didn’t like it, went back on the version control, running git checkout -- . + rm created files, then tried all said above.

It’d be cool if php artisan cache:clear could solve that.

I think the issue should be re-opened.

You can run php artisan package:discover.

Same issue here. We are using Laravel Forge with quick-deploy on our staging environments and the deployment scripts fail in the described cases. The only fix is to manually ssh into the server and rm bootstrap/cache/config.php. Definitely needs a fix!

It’s not a bug in the framework, you can use the forum for discussions or if you have a suggestion please use the https://github.com/laravel/internals repo.

A composer dump-autoload after each deploy would solve your issue but it seems like you have a special installation method out of the norm, so I suggest you seek help on the forums.

Have you tried composer du?

Same here than @LastDragon-ru and @giovannipds This needs a fix.

php artisan package:discover fails. Any artisan command fail because it loads not existing service provider.

That would be nice to add short comment explaining why issue is closed.

I ended up with writing Composer’s pre-autoload-dump script in composer.json file:

{
    "scripts": {
        "pre-autoload-dump": [
            "@php -r \"array_map('unlink', glob('bootstrap/cache/*'));\""
        ],
        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover --ansi"
        ]
    }
}

@themsaid could you please comment why this was closed?

But we don’t have composer on production server

😱 how do you install dependencies then? pushing the vendor folder?

You can close this issue though since this repo is for bug tracking. You can use the forums or the slack channel

If that’s right, it’d be cool if Laravel News get updated: https://laravel-news.com/laravel-5-4-key-too-long-error since it’s one of the first posts related to defaultStringLength.

@rs-sliske , yes. I think that was the problem. I had a called to Schema in AppServiceProvider.php. I just used a try-catch in order to solve it.

@andreshg112

either your app or a package it is using is trying to access database from a service provider / adding an event listener

personally i recently had this with telescope

Yes we push full vendor folder to git. There are reasons for this.

Should clear-compiled command work to delete bootstrap/cache/packages.php? I thought the purpose of this command is to delete cache from bootstrap/cache. But it fails in my particular case. If clear-compiled should not work in this case I will close issue.