ReflectionException in Container.php line 741: Class view does not exist

Question

I'm working on a Laravel 5.1 project with Homestead. I shelled into my Vagrant machine and ran the Composer Update command in an attempt to try to update my project and now I get the following error:

    1. in Container.php line 741
    2. at ReflectionClass->__construct('view') in Container.php line 741
    3. at Container->build('view', array()) in Container.php line 631
    4. at Container->make('view', array()) in Application.php line 674
    5. at Application->make('Illuminate\Contracts\View\Factory') in Container.php line 842
    6. at Container->resolveClass(object(ReflectionParameter)) in Container.php line 805
    7. at Container->getDependencies(array(object(ReflectionParameter)), array()) in Container.php line 776
    8. at Container->build('Illuminate\View\Middleware\ShareErrorsFromSession', array()) in Container.php line 631
    9. at Container->make('Illuminate\View\Middleware\ShareErrorsFromSession', array()) in /home/vagrant/Sites/laravel-basics/vendor/laravel/framework/src/Illuminate/Foundation/Application.php line 674
   10. at Application->make('Illuminate\View\Middleware\ShareErrorsFromSession') in Pipeline.php line 123
   11. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in StartSession.php line 62
   12. at StartSession->handle(object(Request), object(Closure))
   13. at call_user_func_array(array(object(StartSession), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 124
   14. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in AddQueuedCookiesToResponse.php line 37
   15. at AddQueuedCookiesToResponse->handle(object(Request), object(Closure))
   16. at call_user_func_array(array(object(AddQueuedCookiesToResponse), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 124
   17. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in EncryptCookies.php line 59
   18. at EncryptCookies->handle(object(Request), object(Closure))
   19. at call_user_func_array(array(object(EncryptCookies), 'handle'),  array(object(Request), object(Closure))) in Pipeline.php line 124
   20. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in CheckForMaintenanceMode.php line 44
   21. at CheckForMaintenanceMode->handle(object(Request), object(Closure))
   22. at call_user_func_array(array(object(CheckForMaintenanceMode), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 124
   23. at Pipeline->Illuminate\Pipeline\{closure}(object(Request))
   24. at call_user_func(object(Closure), object(Request)) in Pipeline.php line 103
   25. at Pipeline->then(object(Closure)) in Kernel.php line 122
   26. at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 87
   27. at Kernel->handle(object(Request)) in index.php line 54

I'm not sure what broke. I had already been working in Laravel 5.1 and Composer was running just fine. I feel that I have two basic options: 1) try to revert back tot he previous version of Composer or 2) revert to a previous version of my project. However, is there a simpler fix for this?

score 33 · Answer 1 · answered Mar 06 '16 at 22:10

33

I've encountered this error message twice now, so I'm putting the solution here in case I have to google it some time in the future.

This error sometimes occurs because the "/bootstrap/cache" directory isn't writable. Hence, it can't compile a view. The solution is to chmod that directory so that it can be written to.

Voila. You're welcome, Future Me.

answered Mar 06 '16 at 22:10

Jordan Lapp

982
9
19

Thanks past me! You really saved my bacon this time. – Jordan Lapp Apr 20 '16 at 00:14
1

This helped me :) – Sharn White Oct 31 '16 at 23:40
1

Thanks, why can't they just put an error that indicates this! – mic Nov 04 '16 at 11:55
1

upvote +20 - or in my particular case the directory had been removed and it does not attempt to create it – DAB Feb 03 '17 at 17:57
1

Put a Donation link here and you shall become rich :). You just saved my morning! – gthuo Nov 24 '17 at 05:48
@JordanLapp, you made my day! Thank you very much! – Vaha Feb 07 '20 at 12:08
You are a legend – Dng Jul 01 '20 at 19:00

score 8 · Accepted Answer · answered Jan 08 '16 at 07:35

8

Make sure that you have Illuminate\View\ViewServiceProvider listed in the list of providers in your config/app.php file.

Apparently there is no view service in the container and this is the provided that sets it up.

answered Jan 08 '16 at 07:35

jedrzej.kurylo

39,591
9
98
107

That did it. Thank you very much. – MikeAguilera210 Jan 11 '16 at 16:53
The error came up in my case when I tried to update syntax from (just one example) `'Laravel\Socialite\SocialiteServiceProvider',` to `Laravel\Socialite\SocialiteServiceProvider::class,` – Peter Feb 07 '16 at 12:34
I made sure it exists but still getting the error :( – C.Astraea May 05 '21 at 10:49

shanecp · Answer 3 · 2021-01-23T13:52:43.370

For my future reference:

This can happen for a few reasons. Most common,

bootstrap/cache is not writable.
Missing config/view.php or this file has a syntax error.
Try with composer dumpautoload -o
On config/app.php, ViewServiceProvider and View alias must NOT be commented out.

In artisan, you may not see the exact error. If so, go to the error line, and dump the stacktrace. In this case, the file will be , Illuminate/Container/Container.php, line 741 (or the line shown on your screen. Dump the original exception with dd($e), and see where the error started from.

score 0 · Answer 4 · answered Dec 02 '18 at 09:14

0

In my case, the file was not named correctly. The class was declared as :

class NoSessionAccessMiddleware {

but the file was named as NoSessionAccess.php, I just renamed the file to NoSessionAccessMiddleware.php and it fixed the issue.

answered Dec 02 '18 at 09:14

Haris ur Rehman

2,593
30
41

score 0 · Answer 5 · answered Feb 22 '19 at 14:37

Had the same issue, I tried the above solutions with no luck. After running composer dump-autoload, I discovered it was because I had forgotten to install a package (Laravel Excel) I had setup on my dev server that wasn't yet loaded on the production server.

score 0 · Answer 6 · answered Mar 06 '19 at 21:31

I had the same problem after updating my projects namespace. I had to update the composer.json file:

 "psr-4": {
        "App\\": "myforms/app/"
    }

to:

 "psr-4": {
        "App\\": "app/"
    }

On the server, in your source directory, run composer update then composer dump-autoload

score -5 · Answer 7 · answered Jul 16 '18 at 16:51

-5

This also can occur when the permissions on the 'bootstrap' folder and its contents are not right. For me chmodding to writable fixed it.

answered Jul 16 '18 at 16:51

Jonathan Vasquez

7

2

This answer duplicates what https://stackoverflow.com/a/35833239/470749 already says. – Ryan Sep 19 '18 at 03:20

ReflectionException in Container.php line 741: Class view does not exist

7 Answers7