Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath()

[lbausch]

After crafting a new application with laravel new foo and running composer update in the foo directory, the following happens:

Writing lock file
Generating autoload files
PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath() in /tmp/foo/vendor/laravel/framework/src/Illuminate/Foundation/Console/ClearCompiledCommand.php on line 28



  [Symfony\Component\Debug\Exception\FatalErrorException]                             
  Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath()  



Script php artisan clear-compiled handling the post-update-cmd event returned with an error



  [RuntimeException]                                                                                                                                                                                              
  Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath() in /tmp/foo/vendor/laravel/framework/src/Illuminate/Foundation/Console/ClearCompiledCommand  
  .php on line 28                                                                                                                                                                                                 



update [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--lock] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--with-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [packages1] ... [packagesN]

I also saw issue #8124 but the provided solution did not help here.

[coldKingdom]

I had the same problem. Deleted the compiled.php-file in the vendor directory manually, and then it started to work again.

[0xMatt]

Confirming issue on a fresh 5.0.* install as of a few moments ago.

[Helrunar]

Can confirm issue too, delete the compiled.php and it work again

[GrahamCampbell]

Thank you @Helrunar. For anyone reading this, you need to delete your compiled files otherwise the old code will be used by laravel to try to generate the compiled file. Just a technical limitation.

[imuneer]

Can confirm the issue. Let me check deleting the file compiled.php.....

Yes it is working.

[teertz]

Yea, had the same problem.
Deleting the file vendor/compiled.php – helps

[rdjoks]

Yes me too, replace a lot of files in my project directory but that didn't work, had to remove compiled.php, run php artisan clear-compiled and then composer update

[GuillaumeDievart]

@GrahamCampbell You'll envisage to fix this bug ?

[larryweya]

Ran into the same issue but my compiled.php was in storage/framework/compiled.php not in vendor/compiled.php

[GrahamCampbell]

@larryweya Yes, this happens if your file permissions are incorrect and we're not able to write to the vendor folder. We'll use that storage folder as a fallback in 5.0.

[phpclub]

Can confirm issue too, delete the compiled.php

[Ardakilic]

I can confirm this, too. deleting vendor/compiled.php manually and running again works like a charm.