GrahamCampbell
commented
8 years ago What does your code look like please?
Closed ghost closed 8 years ago
GrahamCampbell
commented
8 years ago What does your code look like please?
crynobone
commented
8 years ago This might be a case of upgrading from 5.2 to 5.3 where you need to include Illuminate\Notifications\ NotificationServiceProvider to config/app.php.
progamer
commented
7 years ago I have the same issue and Illuminate\Notifications\NotificationServiceProvider included in config/app.php Any one solved this issue ?
ghost
commented
7 years ago @progamer still have this issue on my production server. Can't find reason why I'm having that error.
progamer
commented
7 years ago @crynobone NotificationServiceProvider already included in config/app.php , @ddctd143 did you solve it on your development env ?
ghost
commented
7 years ago @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:
progamer
commented
7 years ago @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
`
[2016-12-07 20:29:28] local.ERROR: Illuminate\Contracts\Container\BindingResolutionException: Unresolvable dependency resolving [Parameter #0 [
`
ghost
commented
7 years ago @progamer Do you have fresh installation of laravel 5.3 or you upgraded from 5.2 to 5.3.x as I did ?
progamer
commented
7 years ago @ddctd143 no upgraded , but in early stage of development.
danielsdeboer
commented
7 years ago I got this error after an in place upgrade where I forgot to restart my queue workers. Restarting the queue workers fixed it.
avks
commented
7 years ago Anyone has solved the issue? Having the same problem on a fresh Lumen 5.4 installation.
aldee07
commented
7 years ago @danielsdeboer Thanks mate! This works for me. Do you have any clue why?
dlwatersuk
commented
7 years ago @aldee07 queue workers seem to bootstrap and cache the entire application so probably that they held outdated versions of code.
ghost
commented
7 years ago Thats true. You should restart queue after each deployment. Example:
...
cd /home/forge/your-site.com
git pull origin master
composer install --no-interaction --no-dev --prefer-dist
php artisan migrate --force
php artisan cache:clear
php artisan queue:restart # <- this line will prevent from error.
...
gh0sthx
commented
6 years ago Having the same problem when i use factory(App\Post::class,20)->create(); 。who can help me ??
gh0sthx
commented
6 years ago ErrorMessage Illuminate\Contracts\Container\BindingResolutionException with message 'Unresolvable dependency resolving [Parameter #0 [ <required> $app ]] in class Illuminate\Support\Manager'
mingalevme
commented
6 years ago @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.
yosifeldman
commented
6 years ago Same error "Unresolvable dependency resolving [Parameter #0 [ <required> $app ]] in class Illuminate\\Support\\Manager"
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
class MyController extends Controller {
public function __construct(Some $obj) {
.....So, in the above code, the "Some" class requires parameters in constructor, which causes for the issue.
lidrissi
commented
5 years ago This might be a case of upgrading from 5.2 to 5.3 where you need to include
Illuminate\Notifications\ NotificationServiceProvidertoconfig/app.php.
that works for me (y)
a-waris
commented
3 years ago 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
In my case the router parameter "uuid" was being expected as "$emailUuid", so changing it to "$uuid" resolved that for me.
$router->get('/emails/{uuid}', 'EmailController@show');
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.