'ReflectionException' with message 'Class bugsnag does not exist' about bugsnag-laravel

[ConradIrwin]

@Jaspur which version of Laravel are you using? Are you loading the BugsnagLaravelServiceProvider?

[thomasjsn]

I get this error as well

PHP Fatal error:  Uncaught exception 'ReflectionException' with message 'Class bugsnag does not exist' in /var/www/staging/foobar/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php:776
Stack trace:
#0 /var/www/staging/foobar/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php(776): ReflectionClass->__construct('bugsnag')
#1 /var/www/staging/foobar/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php(656): Illuminate\\Container\\Container->build('bugsnag', Array)
#2 /var/www/staging/foobar/laravel/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(613): Illuminate\\Container\\Container->make('bugsnag', Array)
#3 /var/www/staging/foobar/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php(1231): Illuminate\\Foundation\\Application->make('bugsnag')
#4 /var/www/staging/foobar/laravel/vendor/bugsnag/bugsnag-laravel/src/Bugsnag/BugsnagLaravel/BugsnagExceptionHandler.php(25): Illuminate\\Container\\Container->offsetGet('bugsnag')
#5 /var/www/staging/foobar in /var/www/staging/foobar/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 776

I am using Laravel 5.0.16, I am loading the service provider:

'Bugsnag\BugsnagLaravel\BugsnagLaravelServiceProvider',

And alias:

'Bugsnag' => 'Bugsnag\BugsnagLaravel\BugsnagFacade',

I resolved it by making the vendor folder writable by the web server, but I don't get why that should be necessary.

[thomasjsn]

So I did a little bit more testing, I put the permissions on the vendor folder back (not writable by the web-server). No errors until I did a composer update, which did not update any packages but it did generate autoload files and optimized class loader.

Update:
Okey I found the problem... My /vendor folder was not writable, so when I did composer update the services.json file was deleted and the system did not have permissions to create a new one.

[snmaynard]

Glad you solved it (and thanks for letting us know how @HebronNor)!

[tachu]

I'm having the exact same error when running in Google app engine. They require you to run composer update from your environment and then deploying to appEngine. The app engine sandbox makes it so you can't write do disk. IS there a workaround for this? Why does it need to be able to write to disk if its already been composed?

t