Skip to content
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

Closed
neoacevedo opened this issue May 27, 2017 · 9 comments
Closed
Labels
bug This issue is a bug. closed-for-staleness response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.

Comments

@neoacevedo
Copy link

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?

@renepardon
Copy link

I've the same problem with laravel 5.4:

from my composer.json:

"aws/aws-sdk-php-laravel": "^3.1",
"laravel/framework": "5.4.*",

I've deleted the bootstrap/cache/services.php file and vendor directory, did a composer install/update and now I constantly receive this error

Class 'Aws\Laravel\AwsServiceProvider' not found

@renepardon
Copy link

Problem starts when adding AwsServiceProvider to the app.php config file.

@fattchris
Copy link

Same problem here with Lumen 5.1 - any updates?

@fernandominardi
Copy link

Same problem here, in my case with Laravel 5.3.

@renepardon
Copy link

I bought (for monthly rental) a custom storage which I mount to my servers because with this package I can't work right now ;(
Hopefully I find some time to help you fixing this but right now it's not possible for me.

@kstich
Copy link
Contributor

kstich commented Oct 2, 2017

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?

@insign
Copy link

insign commented Jun 26, 2018

Auto discover only worked here using dev-master in composer

@ajredniwja ajredniwja added bug This issue is a bug. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels May 19, 2021
@github-actions
Copy link

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.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels May 20, 2021
@aoneahsan
Copy link

any solution???

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. closed-for-staleness response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Projects
None yet
Development

No branches or pull requests

8 participants