-
Notifications
You must be signed in to change notification settings - Fork 244
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
Class 'Aws\Laravel\AwsServiceProvider' not found after update laravel #115
Comments
I've the same problem with laravel 5.4: from my composer.json:
I've deleted the bootstrap/cache/services.php file and vendor directory, did a composer install/update and now I constantly receive this error
|
Problem starts when adding AwsServiceProvider to the app.php config file. |
Same problem here with Lumen 5.1 - any updates? |
Same problem here, in my case with Laravel 5.3. |
I bought (for monthly rental) a custom storage which I mount to my servers because with this package I can't work right now ;( |
Did everyone with this problem upgrade in place from a previous version? If so, can you please provide what versions of Laravel, Laravel-SDK wrapper, and the SDK you started with and what versions you upgraded to? |
Auto discover only worked here using dev-master in composer |
This issue has not recieved a response in 1 week. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled. |
any solution??? |
Hi. Currently I am using Laravel 4.2 but in my needings I am updating it to latest version. Doing the first step, when I run php composer.phar update or php artisan --version I get the following error:
Class 'Aws\Laravel\AwsServiceProvider' not found in (...)/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php on line 150
Previously I ran php composer.phar update to install all my project dependences and configuring app.php with providers and aliases. Just after that, with above commands I am getting those errors.
Is there some about I have forgotten?
The text was updated successfully, but these errors were encountered: