-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
[5.3] Unresolvable dependency resolving [Parameter #0 [ <required> $app ]] in class Illuminate\Support\Manager #15304
Comments
What does your code look like please? |
This might be a case of upgrading from 5.2 to 5.3 where you need to include |
I have the same issue and Illuminate\Notifications\NotificationServiceProvider included in config/app.php |
@progamer still have this issue on my production server. Can't find reason why I'm having that error. |
@crynobone NotificationServiceProvider already included in config/app.php , |
@progamer Prod env uses beanstalk queue, development uses sync mode ( no queue ). It is only difference between those environments. I tried to switch prod env to sync queue driver, nothing changes. Yes, NotificationServiceProvider is included, and I'm using it alot in my app. Prod environment successfully sends slack notifications, but error still occurs in bugsnag. It is very annoying to receive 50-60 errors each day. Example: |
@ddctd143 my happened with pusher, but the source is the same, i don't think its related to sync/async mode, because i have it on laravel notifications the error shown in both cases when notification is queued or triggered directly
|
@progamer Do you have fresh installation of laravel 5.3 or you upgraded from 5.2 to 5.3.x as I did ? |
@ddctd143 no upgraded , but in early stage of development. |
I got this error after an in place upgrade where I forgot to restart my queue workers. Restarting the queue workers fixed it. |
Anyone has solved the issue? Having the same problem on a fresh Lumen 5.4 installation. |
@danielsdeboer Thanks mate! This works for me. Do you have any clue why? |
@aldee07 queue workers seem to bootstrap and cache the entire application so probably that they held outdated versions of code. |
Thats true. You should restart queue after each deployment.
|
Having the same problem when i use |
ErrorMessage |
@Paladinhanxiao, in my case the error was related to unconfigured Laravel Scout, if you are using Scout, try to remove Laravel\Scout\Searchable-trait from the model and re-run seeding. |
Same error In my case, fixed it by removing the class parameter from the Controller constructor, which was tried to be loaded by DependencyInjection. The issue was that the class required some parameters passed to it's constructor, so the DependencyInjection failed to create an instance. Laravel/Lumen 5.6
So, in the above code, the "Some" class requires parameters in constructor, which causes for the issue. |
that works for me (y) |
Faced this problem upgrading from lumen 5.8 to 6: I was able to solve this by making the parameter matching with the one defined in the route Before: After: |
Description:
When I use pda/pheanstalk queue (3.0.x or 3.1.x ) and queued event listeners, which sends slack Notifications, I receive this error in bugsnag.
And I cant find place which is causing this error.
Full stacktrace:
Steps To Reproduce:
Fire an event, which has queued event listener that uses new 5.3 introduced notification class and sends slack notification.
The text was updated successfully, but these errors were encountered: