New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'ReflectionException' with message 'Class bugsnag does not exist' #41
Comments
@Jaspur which version of Laravel are you using? Are you loading the BugsnagLaravelServiceProvider? |
I get this error as well
I am using Laravel 5.0.16, I am loading the service provider:
And alias:
I resolved it by making the vendor folder writable by the web server, but I don't get why that should be necessary. |
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 Update: |
Glad you solved it (and thanks for letting us know how @HebronNor)! |
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 |
The text was updated successfully, but these errors were encountered: